[go: up one dir, main page]

WO2022001581A1 - 网络、数据传输的方法和装置 - Google Patents

网络、数据传输的方法和装置 Download PDF

Info

Publication number
WO2022001581A1
WO2022001581A1 PCT/CN2021/098388 CN2021098388W WO2022001581A1 WO 2022001581 A1 WO2022001581 A1 WO 2022001581A1 CN 2021098388 W CN2021098388 W CN 2021098388W WO 2022001581 A1 WO2022001581 A1 WO 2022001581A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
priority
core device
packet
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/098388
Other languages
English (en)
French (fr)
Inventor
于斌
畅文俊
贺行健
陈伟
王东辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP21832855.7A priority Critical patent/EP4156563A4/en
Publication of WO2022001581A1 publication Critical patent/WO2022001581A1/zh
Priority to US18/148,914 priority patent/US20230148392A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • 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/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • 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/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/41—Flow control; Congestion control by acting on aggregated flows or links

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and apparatus for network and data transmission.
  • a campus network can be composed of network devices such as egress routers, core switches, aggregation switches, and access switches. To improve service quality, the campus network differentiates service packets of different service types from application servers and forwards them with different priorities.
  • the egress router realizes the service type identification of the service message.
  • the egress router can identify eight service types, and each service type is assigned a corresponding priority.
  • the egress router can identify the service type of the service packet from the application server, add the corresponding priority identifier to the service packet according to the identification result, and forward it to the terminal through the core switch, aggregation switch, access switch, etc.
  • the present application provides a method and device for network and data transmission, which can solve the problems of forwarding congestion and packet loss caused by insufficient identification capability of egress routers and inability to finely identify service types in the related art.
  • the technical solution is as follows:
  • a network in a first aspect, includes a core device and an edge device, wherein the edge device is used to identify a service type of a first service packet from the core device, and send a service type identifier to the core device, The service type identifier is used to identify the service type.
  • the core device is used to store the service priority correspondence, determine the priority corresponding to the service type identifier according to the service priority correspondence, and forward the second service packet according to the priority, wherein the second service packet and the first service The packets belong to the same service flow, and the service priority correspondence includes the mapping from multiple service types to multiple priorities.
  • the edge device with relatively few connected devices realizes the service type identification of the first service packet, and synchronizes the identification result to the core device.
  • the core device can store the service priority correspondence. According to the service type of the first service packet reported by the edge device, the priority corresponding to the service type can be queried in the service priority correspondence, and the priority corresponding to the first service type can be queried based on the priority. A service packet belonging to the same service flow is forwarded.
  • the strong business identification capability of edge devices is fully utilized, and the fine identification of thousands of business types can be realized.
  • the strong entry storage capability of core equipment it can store and record business priority correspondences with thousands of business types and priority correspondences.
  • the edge device is further configured to send a service flow indication of the service flow to which the first service packet belongs.
  • the service flow indication may be an identifier of a service flow, or a quintuple.
  • the quintuple includes a destination address, a source address, a destination port number, a source port number, and a transport layer protocol number.
  • the core device is further configured to establish a corresponding relationship between the service flow and the priority to which the first service packet belongs.
  • the edge device when reporting the service type identifier of the first service packet, may also simultaneously report the service flow indication of the first service packet. In this way, the corresponding relationship between the service flow indication and the priority can be established in the core device.
  • the core device can extract the service flow indication from the received service packet from the upstream, and can query the priority corresponding to the extracted service flow indication in the stored correspondence between the service flow indication and the priority, so as to follow the queried service flow indication.
  • the priority is to forward the service packets.
  • the edge device is further configured to send a delete message to the core device if no service packet belonging to the service flow is received within a preset time period, where the delete message carries a service flow indication.
  • the core device may delete some information in the stored correspondence between the service flow indication and the priority, so as to save storage resources. Determining and deleting those information can be implemented by edge devices. If the edge device does not receive the service packet indicated by the service flow of the first service packet within the preset time period, the edge device sends a delete message to the core device. The delete message carries the service flow indication of the first service packet. The core device deletes the corresponding relationship between the service flow indication and the priority of the first service packet according to the deletion message. Under this mechanism, judging which information to delete is realized by the access device with relatively more idle computing resources, and the core device only needs to perform the corresponding delete operation after receiving the delete message, which can save the computing resources of the core device.
  • the preset duration can be set according to actual needs, such as 1 minute, 5 minutes, etc.
  • the core device is further configured to delete the corresponding relationship between the service flow and the priority according to the deletion message.
  • the core device may delete some information in the stored correspondence between the service flow indication and the priority, so as to save storage resources. Determining and deleting those information can be implemented by the core device itself. If the core device does not receive a service packet whose service flow indication is the service flow indication of the first service packet within a preset time period, it deletes the corresponding relationship between the service flow indication and the priority of the first service packet. Under this mechanism, the core device can delete part of the information in the corresponding relationship between the service flow indication and the priority itself, without interacting with other network devices, which can save data transmission resources.
  • the preset duration can be set according to actual needs, such as 1 minute, 5 minutes, etc.
  • the core device is further configured to set the value of the priority field in the second service packet to a value indicating the priority.
  • the core device may set the value of the priority field in the second service packet to a value indicating the priority, and then check the priority of the second service packet. 2. Service packets are forwarded. In this way, after receiving the second service packet, the edge device may obtain the value of the priority carried in the packet, and forward the second service packet according to the priority identified by the value of the priority.
  • the edge device is further configured to ignore identification of the service type of the second service packet if the value of the priority field in the second service packet received from the core device belongs to the identification-free set.
  • the edge device ignores the service type of the second service packet and directly passes the priority
  • the second packet is forwarded with the priority identified by the value of the field.
  • the value of the priority field of the service packet is usually a fixed value when no priority is assigned
  • the value in the priority field in the second service packet is the value in the identification-free set, it means that A packet belonging to the same service flow as the second service packet is identified as a service type.
  • the identification-free set may be a set composed of other priority values except the above-mentioned fixed values.
  • the edge device is further configured to ignore identifying the service type of the second service packet if the above-mentioned second service packet received from the core device includes a priority field.
  • the core device can add the priority field after assigning the priority to the service packet.
  • the edge After receiving the service packet including the priority field, the device can also ignore the service type identification.
  • the network is an overlay network.
  • the network is a campus network.
  • a method for data transmission is provided.
  • the method is applied to edge devices in a network.
  • the overlay network includes core devices and edge devices.
  • the method includes:
  • the edge device identifies the service type of the first service message from the core device, and sends a service type identifier to the core device, where the service type identifier is used to identify the service type, so that the core device Determine the priority corresponding to the service type identifier according to the stored service priority correspondence, and forward a second service packet according to the priority, wherein the second service packet and the first service packet belonging to the same service flow, the service priority correspondence includes mappings from multiple service types to multiple priorities.
  • the method further includes:
  • the edge device If the edge device does not receive a service packet belonging to the service flow within a preset time period, it sends a deletion message to the core device, where the deletion message carries a service flow indication.
  • the method further includes:
  • the edge device receives the second service packet from the core device and includes a priority field, it ignores identifying the service type of the second service packet, or if it receives all the packets from the core device.
  • the value of the priority field in the second service message belongs to the identification-free set, and the service type of the second service message is ignored.
  • a method for data transmission is provided, the method is applied to a core device in a network, the overlay network includes a core device and an edge device, and the method includes:
  • the core device receiving, by the core device, a service type identifier from the edge device, where the service type identifier is used to identify the service type of the first service packet received by the edge device from the core device;
  • the core device determines the priority corresponding to the service type identifier according to the stored service priority correspondence, and forwards a second service packet according to the priority, wherein the second service packet and the The first service packets belong to the same service flow, and the service priority correspondence includes mappings from multiple service types to multiple priorities.
  • the method also includes:
  • the core device establishes a corresponding relationship between the service flow to which the first service packet belongs and the priority.
  • the method further includes:
  • the core device deletes the correspondence between the service flow to which the first service packet belongs and the priority.
  • the method further includes:
  • the core device does not receive a service packet belonging to the service flow within a preset time period, the corresponding relationship between the service flow and the priority is deleted.
  • a data transmission device is provided, the device is applied to edge devices in a network, the overlay network includes a core device and a plurality of edge devices, and the device includes:
  • an identification module for identifying the service type of the first service message from the core device
  • a sending module configured to send a service type identifier to the core device, where the service type identifier is used to identify the service type, so that the core device determines the correspondence between the service type identifiers according to the stored service priority correspondence and forward the second service packet according to the priority, wherein the second service packet and the first service packet belong to the same service flow, and the service priority correspondence includes multiple services A mapping of types to multiple priorities.
  • the sending module is further configured to:
  • deletion message is sent to the core device, wherein the deletion message carries a service flow indication.
  • the apparatus further includes:
  • a receiving module configured to ignore the identification of the service type of the second service packet if the priority field is included in the second service packet received from the core device, or, if receiving the second service packet from the core device The value of the priority field in the second service packet belongs to the identification-free set, and the service type of the second service packet is ignored.
  • a data transmission device is provided, the device is applied to a core device in a network, the network includes the core device and a plurality of edge devices, and the device includes:
  • a receiving module configured to receive a service type identifier from the edge device, wherein the service type identifier is used to identify the service type of the first service packet received by the edge device from the core device;
  • the determining module is configured to determine the priority corresponding to the service type identifier according to the stored correspondence between the service priorities, and forward the second service packet according to the priority, wherein the second service packet and the The first service packets belong to the same service flow, and the service priority correspondence includes mappings from multiple service types to multiple priorities.
  • the receiving module is further configured to:
  • the device also includes:
  • the establishing module is configured to establish the corresponding relationship between the service flow to which the first service message belongs and the priority.
  • the receiving module is further configured to:
  • a deletion message from the edge device is received, wherein the policy deletion message carries the service flow indication, and the corresponding relationship between the service flow to which the first service message belongs and the priority is deleted.
  • the device further includes:
  • a deletion module configured to delete the corresponding relationship between the service flow and the priority if no service message belonging to the service flow is received within a preset time period.
  • an edge device in a sixth aspect, includes: a processor and a memory, where a program is stored in the memory, and the processor is configured to call the program stored in the memory, so that the edge device executes the following steps: The data transmission method described in the second aspect above.
  • a core device comprising: a processor and a memory, where a program is stored in the memory, and the processor is configured to call the program stored in the memory, so that the core device executes the following steps: The data transmission method described in the third aspect above.
  • a computer-readable storage medium is provided, a computer program is stored in the computer-readable storage medium, and when the computer program is executed on a network device, the network device is made to perform the above-mentioned first aspect Or the method for network configuration described in the second aspect.
  • a computer program product comprising instructions which, when run on a network device, cause the network device to perform the method of network configuration as described in the first or second aspect above.
  • the edge device identifies the service type of the service packet of a certain service flow, and reports the service type corresponding to the service flow to the core device. Since the number of terminals connected to each edge device is relatively small, the edge device can have enough hardware resources to realize fine identification of service types. When the core device forwards other service packets of the session, it does not need to identify the service type of the packets, but only needs to assign priorities and forward them. To sum up, in this application, the identification and priority assignment of service types are implemented in different devices, which can realize fine identification of service types of service packets and assign corresponding priorities, so that different services will not appear. The service packets of different services are identified as the same service type, which can effectively reduce problems such as congestion and packet loss caused by the service packets of different services being identified as the same service type.
  • FIG. 1 is a schematic diagram of a campus network provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a method for data transmission provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for data transmission provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an apparatus for data transmission provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an apparatus for data transmission provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an edge device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a core device provided by an embodiment of the present application.
  • the embodiment of the present application provides a method for data transmission, which can be applied to a network, and the network can be a campus network.
  • an overlay network can be built on the underlying physical network, and the overlay network can also It may be referred to as an overlay network, a virtual network, or the like.
  • network devices can be divided into two roles, one is a core device, and the core device can correspond to a core switch, an egress router, etc. in the underlying network.
  • the other is an edge device, which is a network device used to access user-side terminals, and can correspond to an access device of an underlying network, such as an access switch, an access point (Access Point, AP), and the like.
  • the data transmission method provided by the embodiment of the present application can be applied to the above-mentioned overlay network, and is jointly implemented by an edge device and a core device in the above-mentioned overlay network.
  • the data transmission method provided by the embodiment of the present application may include the following processing flow:
  • Step 201 The edge device identifies the service type of the first service packet from the core device, and sends the service type identifier to the core device.
  • the service type identifier is used to identify the service type, and the first service packet may be the first service packet in a certain downstream service flow received by the edge device.
  • Downlink service flow refers to the service flow sent by the server to the terminal.
  • the terminal in the campus network can interact with the server.
  • the server can send a service flow to the terminal, and the service flow includes multiple service packets.
  • the service message sent by the application server to the terminal needs to be forwarded to the edge device through the core device, and then forwarded by the edge device to the corresponding terminal.
  • the edge device may identify the service type of the first service packet. Specifically, the edge device may store the correspondence between the service feature information and the service type identifier.
  • the correspondence between service feature information and service type identifiers can be shown in Table 1 below:
  • the edge device may query the application layer field of the first service packet, and extract service feature information of the first service packet. Then, in the stored correspondence between the service feature information and the service type identifier, a service type identifier for identifying the service type of the first service message is determined.
  • the service type identifier used to identify the service type of the first service packet can be determined by querying the above Table 1 as "1" ".
  • the edge device may send the service identifier to the core device.
  • the service type identifier may be encapsulated in a service type synchronization message and sent.
  • Step 202 The core device determines the priority corresponding to the service type identifier according to the stored service priority correspondence, and forwards the second service packet according to the priority.
  • the second service packet and the first service packet belong to the same service flow, and the service priority correspondence includes mappings from multiple service types to multiple priorities.
  • the core device receives a service type synchronization message from the edge device.
  • the core device may first determine the service flow to which the service packet belongs. If the service packet and the first service packet corresponding to the above service type identifier belong to the same service flow, the core device may assign a priority to the service packet according to the stored service priority correspondence.
  • the above-mentioned service packet belonging to the same service flow as the first service packet is hereinafter referred to as the second service packet.
  • the edge device When receiving the service packet, the edge device can extract the service flow indication in the service packet. Correspondingly, when the edge device sends the service type identifier to the core device, it can be sent to the core information together with the service flow indication.
  • the target service flow indication may be a quintuple extracted from the first service message, or may be an identifier used to identify a service flow.
  • the quintuple includes a destination address, a source address, a destination port number, a source port number, and a transport layer protocol number.
  • the core device may extract the service flow indication in the second service packet, if the service flow indication extracted in the second service packet and the first service packet sent by the above edge device If the service flow indications are the same, it can be determined that the second service packet and the first service packet belong to the same service flow.
  • the service flow indication of the first service packet may also be carried in the service type synchronization message.
  • the packet format of the service type synchronization message carrying the service type identifier and the service flow indication can be shown in Table 3 below, where the service flow indication takes a quintuple as an example:
  • Edge device address 4 bytes, indicating the Internet Protocol (IP, Internet Protocol) address of the edge device;
  • Core device address 4 bytes, identifying the IP address of the core device
  • Type 2 bytes, the setting value of 1 indicates that the message is used for service type synchronization;
  • Len 2 bytes, indicating the total length of the message
  • Source address 4 bytes, indicating the source IP address of the service packet
  • Destination address 4 bytes, indicating the destination IP address of the service packet
  • Source port number 4 bytes, indicating the port number of the source end of the service packet
  • Destination port number 4 bytes, indicating the port number of the destination end of the service packet
  • Transport layer protocol number 4 bytes, indicating the protocol number of the protocol used by the transport layer;
  • Apptype Indicates the business type identifier
  • the core device can query the stored service priority correspondence after the service flow indication and service type identifier sent by the edge device. , to obtain the value of the priority corresponding to the service type identifier. Then, the corresponding relationship between the above-mentioned service flow indication and the value of the priority may be added to the corresponding relationship between the local service flow and the priority.
  • Table 4 The correspondence between service flow and priority can be shown in Table 4 below:
  • the core device may query the value of the priority corresponding to the service flow indication of the second service packet in the correspondence between the service flow and the priority.
  • the priority identified by the value of the priority corresponding to the service flow indication of the queried second service packet is the priority assigned to the second service packet.
  • the priority corresponding to the second service packet is the same as the priority corresponding to the first service.
  • the core device may set the value of the priority field in the second service packet to a value indicating the priority. Settings here can include modifications or additions. In this way, after receiving the second service packet, the edge device can forward the second service packet to the terminal according to the identified priority of the priority carried therein.
  • the edge device ignores the service type of the second service packet, and is directly identified by the value of the priority field.
  • the priority of the second packet is forwarded.
  • the value of the priority field of the service packet is usually a fixed value when no priority is assigned, if the value in the priority field in the second service packet is the value in the identification-free set, it means that A packet belonging to the same service flow as the second service packet is identified as a service type.
  • the identification-free set may be a set composed of other priority values except the above-mentioned fixed values.
  • the core device may delete some information in the stored correspondence between service flows and priorities, so as to save storage resources.
  • the following two deletion mechanisms are available:
  • the core device If the core device does not receive a service packet indicating that the service flow is the target service flow within a preset period of time after receiving the service packet indicated by the target service flow last time, it deletes the target service.
  • the correspondence between the flow indication and the value of the priority Under this mechanism, the core device can delete part of the information in the corresponding relationship between the service flow and the priority itself, without interacting with other network devices, which can save data transmission resources.
  • the preset duration can be set according to actual needs, such as 1 minute, 5 minutes, etc.
  • Mechanism 2 If the edge device does not receive a service packet indicating that the service flow is the target service flow within a preset period of time after receiving the service packet indicated by the target service flow last time, the edge device will send a message to the core device. A delete message is sent, wherein the delete message carries the indication of the target service flow. The core device deletes the corresponding relationship between the target service flow indication and the priority value according to the deletion message. Under this mechanism, judging which information to delete is realized by the access device with relatively more idle computing resources, and the core device only needs to perform the corresponding delete operation after receiving the policy deletion message, which can save the computing resources of the core device. .
  • the preset duration can be set according to actual needs, such as 1 minute, 5 minutes, etc.
  • the message format of the delete message sent by the edge device to the core device can be the same as the message format shown in Table 3 above. It is only necessary to fill in the set value of the Action field as 0, and the rest of the fields need to be set as 0. The actual situation can be added.
  • the message format of the deletion message also deletes the Apptype field on the basis of the message format shown in Table 3 above, fills the set value of the Action field with 0, and adds other fields according to the actual situation.
  • the packet format of the delete message can be shown in Table 5 below:
  • the edge device identifies the service type of the service packet of a certain service flow, and reports the service type corresponding to the service flow to the core device. Since the number of terminals connected to each edge device is relatively small, the edge device can have enough hardware resources to realize fine identification of service types. When the core device forwards other service packets of the session, it does not need to identify the service type of the packets, but only needs to assign priorities and forward them. To sum up, in this application, the identification and priority assignment of service types are implemented in different devices, which can realize fine identification of service types of service packets and assign corresponding priorities, so that different services will not appear. The service packets of different services are identified as the same service type, which can effectively reduce problems such as congestion and packet loss caused by the service packets of different services being identified as the same service type.
  • an embodiment of the present application provides a method for data transmission, and the processing flow of the method may include the following steps:
  • Step 301 The edge device receives the first service packet from the core device.
  • Step 302 The edge device identifies the target service type of the first service packet in the first service packet, and extracts the target service flow indication in the first service packet.
  • Step 303 The edge device sends a service type synchronization message to the core device.
  • the service type synchronization message carries a target service type identifier and a target service flow indication, and the target service type identifier is used to identify the target service type.
  • Step 304 The core device determines the target priority corresponding to the target service type according to the service priority corresponding relationship, and establishes the corresponding relationship between the target service flow indication and the target priority.
  • Step 305 The core device receives the second service message.
  • Step 306 The core device extracts the service flow indication in the second service packet, determines that the service flow indication in the second service packet is the target service flow indication, and obtains the value of the target priority corresponding to the target service flow indication, and in the second Set the value of the target priority in the service packet.
  • Step 307 The core device forwards the second service packet carrying the value of the target priority to the edge device according to the target priority.
  • Step 308 The edge device determines that the value of the priority field in the second service packet belongs to the identification-free set, ignores the service type of the identification second service packet, and forwards the second service packet to the terminal according to the target priority.
  • Step 309 If the edge device does not receive a service packet indicating that the service flow is the target service flow indication within a preset time period, it sends a delete message to the core device.
  • the delete message carries the target service flow indication.
  • Step 310 The core device deletes the corresponding relationship between the target priority and the target service flow indication according to the deletion message.
  • the edge device identifies the service type of the service packet of a certain service flow, and reports the service type corresponding to the service flow to the core device. Since the number of terminals connected to each edge device is relatively small, the edge device can have enough hardware resources to realize fine identification of service types. When the core device forwards other service packets of the session, it does not need to identify the service type of the packets, but only needs to assign priorities and forward them. To sum up, in this application, the identification and priority assignment of service types are implemented in different devices, which can realize fine identification of service types of service packets and assign corresponding priorities, so that different services will not appear. The service packets of different services are identified as the same service type, which can effectively reduce problems such as congestion and packet loss caused by the service packets of different services being identified as the same service type.
  • an embodiment of the present application also provides a data transmission device, which is applied to edge devices in a network, where the network includes core devices and edge devices.
  • the device includes:
  • the identification module 410 is configured to identify the service type of the first service packet from the core device. Specifically, the identification function mentioned in the above step 201 and other implicit steps can be implemented.
  • a sending module 420 configured to send a service type identifier to the core device, where the service type identifier is used to identify the service type, so that the core device determines the service type identifier according to the stored service priority correspondence corresponding priority, and forward the second service packet according to the priority, wherein the second service packet and the first service packet belong to the same service flow, and the service priority correspondence includes multiple Mapping of business types to multiple priorities.
  • the sending function mentioned in the above step 201 and other implicit steps can be implemented.
  • the sending module 420 is further configured to send a deletion message to the core device if no service packet belonging to the service flow is received within a preset time period, wherein the deletion The message carries the service flow indication.
  • the device further includes:
  • a receiving module configured to ignore the identification of the service type of the second service packet if the priority field is included in the second service packet received from the core device, or, if receiving the second service packet from the core device The value of the priority field in the second service packet belongs to the identification-free set, and the service type of the second service packet is ignored.
  • the edge device identifies the service type of the service packet of a certain service flow, and reports the service type corresponding to the service flow to the core device. Since the number of terminals connected to each edge device is relatively small, the edge device can have enough hardware resources to realize fine identification of service types. When the core device forwards other service packets of the session, it does not need to identify the service type of the packets, but only needs to assign priorities and forward them. To sum up, in this application, the identification and priority assignment of service types are implemented in different devices, which can realize fine identification of service types of service packets and assign corresponding priorities, so that different services will not appear. The service packets of different services are identified as the same service type, which can effectively reduce problems such as congestion and packet loss caused by the service packets of different services being identified as the same service type.
  • the data transmission device provided in the above embodiment performs data transmission
  • only the division of the above functional modules is used as an example for illustration.
  • the above functions may be allocated to different functional modules as required. , that is, dividing the internal structure of the edge device into different functional modules to complete all or part of the functions described above.
  • the data transmission apparatus and the data transmission method embodiments provided by the above embodiments belong to the same concept, and the specific implementation process thereof is detailed in the method embodiments, which will not be repeated here.
  • an embodiment of the present application also provides a data transmission device, the device is applied to a core device in a network, and the network includes a core device and an edge device. As shown in FIG. 5 , the device includes:
  • the receiving module 510 is configured to receive a service type identifier from the edge device, where the service type identifier is used to identify the service type of the first service packet received by the edge device from the core device. Specifically, the receiving function of the core device mentioned in the above step 201 and other implicit steps can be implemented.
  • the determining module 520 is configured to determine the priority corresponding to the service type identifier according to the stored correspondence between the service priorities, and forward the second service packet according to the priority, wherein the second service packet and the The first service packets belong to the same service flow, and the service priority correspondence includes mappings from multiple service types to multiple priorities. Specifically, the determination function of the core device mentioned in the above step 202 and other implicit steps can be implemented.
  • the receiving module 510 is further configured to:
  • the device also includes:
  • the establishing module is configured to establish the corresponding relationship between the service flow to which the first service message belongs and the priority.
  • the receiving module 510 is further configured to:
  • a deletion message from the edge device is received, wherein the policy deletion message carries the service flow indication, and the corresponding relationship between the service flow to which the first service message belongs and the priority is deleted.
  • the device further includes:
  • a deletion module configured to delete the corresponding relationship between the service flow and the priority if no service message belonging to the service flow is received within a preset time period.
  • the edge device identifies the service type of the service packet of a certain service flow, and reports the service type corresponding to the service flow to the core device. Since the number of terminals connected to each edge device is relatively small, the edge device can have enough hardware resources to realize fine identification of service types. When the core device forwards other service packets of the session, it does not need to identify the service type of the packets, but only needs to assign priorities and forward them. To sum up, in this application, the identification and priority assignment of service types are implemented in different devices, which can realize fine identification of service types of service packets and assign corresponding priorities, so that different services will not appear. The service packets of different services are identified as the same service type, which can effectively reduce problems such as congestion and packet loss caused by the service packets of different services being identified as the same service type.
  • the data transmission device provided in the above embodiment performs data transmission
  • only the division of the above functional modules is used as an example for illustration.
  • the above functions may be allocated to different functional modules as required. , that is, dividing the internal structure of the core device into different functional modules to complete all or part of the functions described above.
  • the data transmission apparatus and the data transmission method embodiments provided by the above embodiments belong to the same concept, and the specific implementation process thereof is detailed in the method embodiments, which will not be repeated here.
  • the edge device 600 includes a processor 601 , a memory 602 , a communication interface 603 and a bus 604 .
  • the processor 601 , the memory 602 and the communication interface 603 are communicatively connected to each other through a bus 604 .
  • the connection between the processor 601, the memory 602 and the communication interface 603 shown in FIG. 6 is only exemplary, and during the implementation process, the processor 601, the memory 602 and the communication interface 603 may also be They are communicatively connected to each other using other connections than the bus 604 .
  • the memory 602 is used for storing instructions 6021 and data 6022 .
  • the memory 602 may be various types of storage media, for example, the memory 602 may be random access memory (RAM), read-only memory (ROM), non-volatile RAM (non-volatile RAM) , NVRAM), programmable ROM (programmable ROM, PROM), erasable PROM (erasable PROM, EPROM), electrically erasable PROM (electrically erasable PROM, EEPROM), flash memory, optical memory and registers, etc. Also, the memory 602 may include hard disk and/or memory.
  • the processor 601 may be a general-purpose processor, and the general-purpose processor may be a processor that performs specific steps and/or operations by reading and executing instructions (eg, instructions 6021 ) stored in a memory (eg, memory 602 ).
  • the processor may use data (eg, data 6022 ) stored in memory (eg, memory 602 ) in performing the steps and/or operations described above.
  • a general-purpose processor may be, for example, but not limited to, a central processing unit (CPU).
  • the processor 601 can also be a special-purpose processor, which can be a processor specially designed to perform certain steps and/or operations, and the special-purpose processor can be, for example, but not limited to, a digital signal processor ( digital signal processor, DSP), application-specific integrated circuit (application-specific integrated circuit, ASIC) and field-programmable gate array (field-programmable gate array, FPGA), etc.
  • the processor 601 may also be a combination of multiple processors, such as a multi-core processor.
  • the processor 601 may include one or more circuits to perform all or part of the steps of the data transmission method provided by the above embodiments.
  • the communication interface 603 may include an input/output (input/output, I/O) interface, a physical interface, a logical interface, and other interfaces for realizing the interconnection of devices within the edge device 600, and for realizing the connection between the edge device 600 and other An interface through which devices, such as network devices or workstations, are interconnected.
  • the physical interface can be a gigabit ethernet (GE), which can be used to interconnect the edge device 600 with other devices (such as network devices or workstations), and the logical interface is an internal interface of the edge device 600, which can be used for interconnection. It is used to realize the device interconnection inside the edge device 600 .
  • GE gigabit ethernet
  • the communication interface 603 can be used for the edge device 600 to communicate with other network devices and/or workstations, for example, the communication interface 603 is used for sending and receiving messages between the edge device 600 and other network devices.
  • the bus 604 may be any type of communication bus for realizing interconnection of the processor 601, the memory 602 and the communication interface 603, such as a system bus.
  • the above-mentioned devices may be respectively arranged on chips that are independent of each other, or at least part or all of them may be arranged on the same chip. Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the needs of product design.
  • the embodiments of the present application do not limit the specific implementation form of the above device.
  • the core device 700 includes a processor 701 , a memory 702 , a communication interface 703 and a bus 704 .
  • the processor 701 , the memory 702 and the communication interface 703 are communicatively connected to each other through a bus 704 .
  • the connection between the processor 701, the memory 702 and the communication interface 703 shown in FIG. 7 is only exemplary, and during the implementation process, the processor 701, the memory 702 and the communication interface 703 may also be They are communicatively connected to each other using other connections than the bus 704 .
  • the memory 702 is used for storing instructions 7021 and data 7022 .
  • the memory 702 may be various types of storage media, for example, the memory 702 may be random access memory (RAM), read-only memory (ROM), non-volatile RAM (non-volatile RAM) , NVRAM), programmable ROM (programmable ROM, PROM), erasable PROM (erasable PROM, EPROM), electrically erasable PROM (electrically erasable PROM, EEPROM), flash memory, optical memory and registers, etc. Also, the memory 702 may include hard disk and/or memory.
  • the processor 701 may be a general-purpose processor, and the general-purpose processor may be a processor that performs specific steps and/or operations by reading and executing instructions (eg, instructions 7021 ) stored in a memory (eg, memory 702 ).
  • the processor may use data (eg, data 7022 ) stored in memory (eg, memory 702 ) in performing the steps and/or operations described above.
  • a general-purpose processor may be, for example, but not limited to, a central processing unit (CPU).
  • the processor 701 can also be a special purpose processor, which can be a processor specially designed to perform certain steps and/or operations, and the special purpose processor can be, for example, but not limited to, a digital signal processor ( digital signal processor, DSP), application-specific integrated circuit (application-specific integrated circuit, ASIC) and field-programmable gate array (field-programmable gate array, FPGA), etc.
  • the processor 701 may also be a combination of multiple processors, such as a multi-core processor.
  • the processor 701 may include one or more circuits to perform all or part of the steps of the data transmission method provided by the above embodiments.
  • the communication interface 703 may include an input/output (input/output, I/O) interface, a physical interface, a logical interface, and other interfaces used to realize the interconnection of devices within the core device 700, as well as interfaces used to realize the interconnection between the core device 700 and other An interface through which devices, such as network devices or workstations, are interconnected.
  • the physical interface can be a gigabit ethernet (GE), which can be used to interconnect the core device 700 with other devices (such as network devices or workstations), and the logical interface is an interface inside the core device 700, which can be used to interconnect the core device 700 with other devices (such as network devices or workstations). It is used to realize the device interconnection inside the core device 700 .
  • GE gigabit ethernet
  • the communication interface 703 can be used for the core device 700 to communicate with other network devices and/or workstations, for example, the communication interface 703 is used for sending and receiving messages between the core device 700 and other network devices.
  • the bus 704 may be any type of communication bus used for realizing interconnection of the processor 701, the memory 702 and the communication interface 703, such as a system bus.
  • the above-mentioned devices may be respectively arranged on chips that are independent of each other, or at least part or all of them may be arranged on the same chip. Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the needs of product design.
  • the embodiments of the present application do not limit the specific implementation form of the above device.
  • the computer program product includes one or more computer instructions, and when the computer program instructions are loaded and executed on a device, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that the device can access, or a data storage device such as a server, data center, or the like that includes an integration of one or more available media.
  • the usable medium may be a magnetic medium (such as a floppy disk, a hard disk, and a magnetic tape, etc.), an optical medium (such as a digital video disk (Digital Video Disk, DVD), etc.), or a semiconductor medium (such as a solid-state disk, etc.).

Landscapes

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

Abstract

公开了一种网络、数据传输的方法和装置，属于通信技术领域。该网络包括核心设备和边缘设备。边缘设备识别来自核心设备的第一业务报文的业务类型，并向核心设备上报第一报文的业务类型标识。核心设备根据存储的业务优先级对应关系，确定该业务类型标识对应的优先级，根据该优先级转发与第一业务报文属于相同业务流的业务报文。利用了边缘设备较强的业务识别能力，可以实现对上千种业务类型的精细识别，并且利用了核心设备较强的表项存储能力，可以存储记录有上千种业务类型和优先级对应关系。有效的避免了无法对业务类型精细识别，对不同业务类型的业务报文分配相同优先级，导致的传输拥塞、丢包等问题。

Description

网络、数据传输的方法和装置
本申请要求于2020年06月30日提交的申请号为202010615469.1、发明名称为“网络、数据传输的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种网络、数据传输的方法和装置。
背景技术
通常园区网络可以由出口路由器、核心交换机、汇聚交换机、接入交换机等网络设备组成。为了提高服务质量，园区网络会对来自应用服务器的不同业务类型的业务报文进行区分，已不同优先级进行转发。
目前，由出口路由器实现对业务报文的业务类型识别，根据现有规范出口路由器可识别八种业务类型，对于每种业务类型分配有对应的优先级。出口路由器可以将来自应用服务器的业务报文进行业务类型识别，并根据识别结果在业务报文中添加对应的优先级标识，经由核心交换机、汇聚交换机、接入交换机等转发至终端。
在实际应用中，经过出口路由器的业务报文的业务类型有成百上千种，然而由于出口路由器的硬件资源限制，无法对其一一识别，而仅能识别为八种业务类型。这样会出现实际属于不同业务的两个业务报文被识别为相同业务类型，而分配相同优先级，在后续交换机的转发过程中可能会由于具有相同优先级，出现拥塞、丢包等问题。
发明内容
本申请提供了一种网络、数据传输的方法和装置，能够解决相关技术中由于出口路由器识别能力不足，无法对业务类型进行精细识别，而导致的转发拥塞、丢包等问题。所述技术方案如下：
第一方面，提供了一种网络，该叠加网络包括核心设备和边缘设备，其中，边缘设备，用于识别来自核心设备的第一业务报文的业务类型，并向核心设备发送业务类型标识，业务类型标识用于标识所述业务类型。
核心设备，用于存储业务优先级对应关系，根据业务优先级对应关系，确定业务类型标识对应的优先级，并根据优先级转发第二业务报文，其中，第二业务报文和第一业务报文属于相同业务流，业务优先级对应关系包括多种业务类型到多个优先级的映射。
在本申请提供的方案中，由连接设备相对较少的边缘设备实现对第一业务报文的业务类型识别，并将识别结果同步至核心设备。核心设备可以存储业务优先级对应关系，根据边缘设备上报的第一业务报文的业务类型，可以在业务优先级对应关系中查询出该业务类型对应的优先级，并以该优先级对与第一业务报文属于相同业务流的业务报文进行转发。
在该方案中，充分利用了边缘设备较强的业务识别能力，可以实现对上千种业务类型的精细识别。并且利用了核心设备较强的表项存储能力，可以存储记录有上千种业务类型和优 先级对应关系的业务优先级对应关系。
在一种可能的实现方式中，边缘设备还用于发送第一业务报文所属业务流的业务流指示。
在本申请提供的方案中，业务流指示可以为业务流的标识，还可以为五元组。其中，五元组包括目的地址、源地址、目的端口号、源端口号和传输层协议号。
在一种可能的实现方式中，核心设备，还用于建立所述第一业务报文所属业务流和优先级的对应关系。
在本申请提供的方案中，边缘设备在上报第一业务报文的业务类型标识时，还可以同时上报第一业务报文的业务流指示。这样，在核心设备中可以建立业务流指示和优先级的对应关系。核心设备可以对接收到的来自上行的业务报文提取业务流指示，并可以在存储的业务流指示和优先级的对应关系中查询该提取的业务流指示对应的优先级，以按照查询到的优先级对该业务报文进行转发。
在一种可能的实现方式中，边缘设备还用于如果在预设时长内未接收到属于业务流的业务报文，则向核心设备发送删除消息，其中，删除消息携带业务流指示。
在本申请提供的方案中，核心设备可以对存储的业务流指示和优先级的对应关系中的部分信息进行删除，以节省存储资源。判断删除那些信息，可以由边缘设备实现。边缘设备如果在预设时长内，未接收到业务流指示为第一业务报文的业务流指示的业务报文，则向核心设备发送删除消息。其中，删除消息携带所述第一业务报文的业务流指示。核心设备则根据删除消息，删除第一业务报文的业务流指示和优先级的对应关系。此机制下，判断对哪些信息进行删除由闲置计算资源相对较多接入设备实现，而核心设备只需要在接收到删除消息后，执行相应的删除操作即可，可以节省核心设备的计算资源。其中，预设时长可以根据实际需求设置，如1分钟、5分钟等。
在一种可能的实现方式中，核心设备还用于根据删除消息，删除业务流和优先级的对应关系。
在本申请提供的方案中，核心设备可以对存储的业务流指示和优先级的对应关系中的部分信息进行删除，以节省存储资源。判断删除那些信息，可以由核心设备自己实现。核心设备如果在预设时长内，未接收到业务流指示为第一业务报文的业务流指示的业务报文，则删除第一业务报文的业务流指示和优先级的对应关系。此机制下，可以由核心设备自行实现对业务流指示和优先级的对应关系中的部分信息进行删除，无需与其余网络设备交互，可以节省数据传输资源。其中，预设时长可以根据实际需求设置，如1分钟、5分钟等。
在一种可能的实现方式中，核心设备，还用于将第二业务报文中的优先级字段的值设置为指示所述优先级的值。
在本申请提供的方案中，核心设备在查询出第二业务报文的优先级后，可以将第二业务报文中的优先级字段的值设置为指示所述优先级的值，再对第二业务报文进行转发。这样，边缘设备在接收到第二业务报文后，可以获取其中携带的优先级的值，根据优先级的值所标识的优先级对该第二业务报文进行转发即可。
在一种可能的实现方式中，边缘设备还用于如果接收来自核心设备的第二业务报文中的优先级字段的值属于免识别集合，忽略识别第二业务报文的业务类型。
在本申请提供的方案中，边缘设备如果接收来自核心设备的第二业务报文中的优先级字段的值属于免识别集合，则忽略识别第二业务报文的业务类型，直接通过该优先级字段的值 所标识的优先级转发该第二报文。此处，由于在未分配优先级的情况下，业务报文的优先级字段的值通常为固定值，如果在第二业务报文中优先级字段中的值为免识别集合中值，则说明有与该第二业务报文属于相同业务流的报文被识别业务类型。免识别集合可以为除上述固定值以外的其余优先级的值所组成的集合。
在一种可能的实现方式中，边缘设备，还用于如果接收来自核心设备的上述第二业务报文中包括优先级字段，则忽略识别第二业务报文的业务类型。
在本申请提供的方案中，对于在未分配优先级时，业务报文中不包括优先级字段的情况，则核心设备在对业务报文分配优先级后可以添加优先级字段，相应的，边缘设备在接收到包括有优先级字段的业务报文后，也可以忽略业务类型识别。
在一种可能的实现方式中，该网络为叠加网络。
在一种可能的实现方式中，该网络为园区网络。
第二方面，提供了一种数据传输的方法，该方法应用于网络中的边缘设备，叠加网络包括核心设备和边缘设备，该方法包括：
所述边缘设备识别来自所述核心设备的第一业务报文的业务类型，并向所述核心设备发送业务类型标识，所述业务类型标识用于标识所述业务类型，以使所述核心设备根据存储的业务优先级对应关系，确定所述业务类型标识对应的优先级，并根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
在一种可能的实现方式中，该方法还包括：
所述边缘设备如果在预设时长内未接收到属于所述业务流的业务报文，则向所述核心设备发送删除消息，其中，所述删除消息携带业务流指示。
在一种可能的实现方式中，该方法还包括：
所述边缘设备如果接收来自所述核心设备的所述第二业务报文中包括优先级字段，则忽略识别所述第二业务报文的业务类型，或者，如果接收来自所述核心设备的所述第二业务报文中的优先级字段的值属于免识别集合，忽略识别所述第二业务报文的业务类型。
第三方面，提供了一种数据传输的方法，该方法应用于网络中的核心设备，叠加网络包括核心设备和边缘设备，该方法包括：
所述核心设备接收来自所述边缘设备的业务类型标识，其中，所述业务类型标识用于标识所述边缘设备接收到的来自所述核心设备的第一业务报文的业务类型；
所述核心设备根据存储的所述业务优先级对应关系，确定所述业务类型标识对应的优先级，根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
在一种可能的实现方式中，
所述方法还包括：
所述核心设备接收来自所述边缘设备的所述第一业务报文所属业务流的业务流指示；
所述核心设备建立所述第一业务报文所属业务流和所述优先级的对应关系。
在一种可能的实现方式中，所述方法还包括：
所述核心设备接收来自所述边缘设备的删除消息，其中，所述策略删除消息携带所述业务流指示；
所述核心设备删除所述第一业务报文所属业务流和所述优先级的对应关系。
在一种可能的实现方式中，该方法还包括：
所述核心设备如果在预设时长内未接收到属于所述业务流的业务报文，则删除所述业务流和所述优先级的对应关系。
第四方面，提供了一种数据传输的装置，该装置应用于网络中的边缘设备，叠加网络包括核心设备和多个边缘设备，该装置包括：
识别模块，用于识别来自所述核心设备的第一业务报文的业务类型；
发送模块，用于向所述核心设备发送业务类型标识，所述业务类型标识用于标识所述业务类型，以使所述核心设备根据存储的业务优先级对应关系，确定所述业务类型标识对应的优先级，并根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
在一种可能的实现方式中，所述发送模块还用于：
如果在预设时长内未接收到属于所述业务流的业务报文，则向所述核心设备发送删除消息，其中，所述删除消息携带业务流指示。
在一种可能的实现方式中，所述装置还包括：
接收模块，用于如果接收来自所述核心设备的所述第二业务报文中包括优先级字段，则忽略识别所述第二业务报文的业务类型，或者，如果接收来自所述核心设备的所述第二业务报文中的优先级字段的值属于免识别集合，忽略识别所述第二业务报文的业务类型。
第五方面，提供了一种数据传输的装置，该装置应用于网络中的核心设备，网络包括所述核心设备和多个边缘设备，该装置包括：
接收模块，用于接收来自所述边缘设备的业务类型标识，其中，所述业务类型标识用于标识所述边缘设备接收到的来自所述核心设备的第一业务报文的业务类型；
确定模块，用于根据存储的所述业务优先级对应关系，确定所述业务类型标识对应的优先级，根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
在一种可能的实现方式中，所述接收模块，还用于：
接收来自所述边缘设备的所述第一业务报文所属业务流的业务流指示；
所述装置还包括：
建立模块，用于建立所述第一业务报文所属业务流和所述优先级的对应关系。
在一种可能的实现方式中，所述接收模块还用于：
接收来自所述边缘设备的删除消息，其中，所述策略删除消息携带所述业务流指示，删除所述第一业务报文所属业务流和所述优先级的对应关系。
在一种可能的实现方式中，该装置还包括：
删除模块，用于如果在预设时长内未接收到属于所述业务流的业务报文，则删除所述业务流和所述优先级的对应关系。
第六方面，提供了一种边缘设备，该边缘设备包括：处理器和存储器，所述存储器中存储有程序，所述处理器用于调用所述存储器中存储的程序，使得所述边缘设备执行如上述第二方面所述的数据传输的方法。
第七方面，提供了一种核心设备，该核心设备包括：处理器和存储器，所述存储器中存储有程序，所述处理器用于调用所述存储器中存储的程序，使得所述核心设备执行如上述第三方面所述的数据传输的方法。
第八方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序在网络设备上运行时，使得所述网络设备执行如上述第一方面或第二方面所述的网络配置的方法。
第九方面，提供了一种包含指令的计算机程序产品，当其在网络设备上运行时，使得所述网络设备执行如上述第一方面或第二方面所述的网络配置的方法。
本申请提供的技术方案带来的有益效果是：
在本申请实施例中，由边缘设备识别某业务流的业务报文的业务类型，并将该业务流对应的业务类型上报至核心设备。由于每个边缘设备所连接的终端数量相对较少，那么，边缘设备就可以有足够的硬件资源实现对业务类型的精细识别。核心设备在转发该会话的其他业务报文时，无需对其进行业务类型识别，只需对其分配优先级并转发即可。综上，在本申请中，对业务类型的识别和优先级分配放在不同设备中实现，可以实现对业务报文的业务类型进行精细识别，并分配对应的优先级，则不会出现不同业务的业务报文被识别为相同业务类型，可以有效减少由于不同业务的业务报文被识别为相同业务类型而造成的拥塞、丢包等问题。
附图说明
图1是本申请实施例提供的一种园区网络示意图；
图2是本申请实施例提供的一种数据传输的方法流程图；
图3是本申请实施例提供的一种数据传输的方法流程图；
图4是本申请实施例提供的一种数据传输的装置的结构示意图；
图5是本申请实施例提供的一种数据传输的装置的结构示意图；
图6是本申请实施例提供的一种边缘设备的结构示意图；
图7是本申请实施例提供的一种核心设备的结构示意图。
具体实施方式
本申请实施例提供了一种数据传输的方法，该方法可以应用于网络中，该网络可以园区网络，在园区网络构建时，可以在底层(underlay)物理网络上搭建叠加网络，该叠加网络还可以称为上层(overlay)网络、虚拟网络等。如图1所示，在本申请实施例的叠加网络中，网络设备可以分为两种角色，一种为核心设备，核心设备可以对应于底层网络中的核心交换 机、出口路由器等。另外一种为边缘设备，该边缘设备为用于接入用户侧终端的网络设备，可以对应于底层网络的接入设备，如接入交换机、接入点(Access Point，AP)等。
本申请实施例所提供的一种数据传输的方法可以应用于上述叠加网络中，由上述叠加网络中的边缘设备和核心设备共同实现。参见图2，本申请实施例所提供的数据传输的方法可以包括如下处理流程：
步骤201、边缘设备识别来自核心设备的第一业务报文的业务类型，并向核心设备发送业务类型标识。
其中，业务类型标识用于标识业务类型，第一业务报文可以为边缘设备接收到的第一个某下行业务流中的业务报文。下行业务流是指服务端向终端发送的业务流。
在实施中，园区网络中的终端可以和服务端之间进行交互。服务端可以向终端发送业务流，在业务流中包括多个业务报文。应用服务器向终端发送的业务报文需要经由核心设备转发至边缘设备，再由边缘设备转发至相应的终端。
边缘设备在接收到某业务流中的第一业务报文后，可以对该第一业务报文进行业务类型识别。具体的，在边缘设备可以存储有业务特征信息和业务类型标识的对应关系。业务特征信息和业务类型标识的对应关系可以如下表1所示：
表1
业务特征信息 业务类型标识
A 1
B 2
C 3
…… ……
边缘设备在接收到第一业务报文后，可以查询该第一业务报文的应用层字段，提取出该第一业务报文的业务特征信息。然后，在存储的业务特征信息和业务类型标识的对应关系中，确定出用于标识该第一业务报文的业务类型的业务类型标识。
例如，边缘设备提取出该第一业务报文的业务特征信息为“A”，则可以通过查询上述表1以确定出用于标识该第一业务报文的业务类型的业务类型标识为“1”。
在确定出用于标识该第一业务报文的业务类型的业务类型标识后，边缘设备可以向核心设备发送该业务标识。在一种可能的实现方式中，在发送业务类型标识时，可以将业务类型标识封装在业务类型同步消息中发送。
步骤202、核心设备根据存储的业务优先级对应关系，确定业务类型标识对应的优先级，根据优先级转发第二业务报文。
其中，第二业务报文和第一业务报文属于相同业务流，业务优先级对应关系包括多种业务类型到多个优先级的映射。
在实施中，核心设备接收来自边缘设备的业务类型同步消息。核心设备在接收到业务报文时，可以先判断该业务报文所属的业务流。如果该业务报文与上业务类型标识所对应的第一业务报文属于相同业务流，核心设备则可以根据存储的业务优先级对应关系，对该业务报文分配优先级。
上述业务优先级对应关系可以以业务类型标识和优先级的值的对应关系进行表示，如下表2所示：
表2
业务类型标识 优先级的值
1 0
2 1
3 2
…… ……
为了与第一业务报文区分，下面对于上述与第一业务报文属于相同业务流的业务报文称为第二业务报文。
下面对于核心设备判断该第二业务报文与上述第一业务报文属于相同业务流的方法进行说明：
边缘设备在接收到业务报文时，可以提取业务报文中的业务流指示。相应的，边缘设备向核心设备发送业务类型标识时，可以连同业务流指示一起发送至核心信息。该目业务流指示可以为第一业务报文中提取的五元组，也可以为用于标识业务流的标识。其中，五元组包括目的地址、源地址、目的端口号、源端口号和传输层协议号。核心设备在接收到第二业务报文时，可以提取该第二业务报文中的业务流指示，如果该第二业务报文中提取的业务流指示和上述边缘设备发送的第一业务报文的业务流指示相同，则可以确定该第二业务报文和第一业务报文属于相同业务流。
在边缘设备通过业务类型同步消息的方式向核心设备发送业务类型标识的情况下，上述第一业务报文的业务流指示也可以一起携带在该业务类型同步消息中。携带有业务类型标识和业务流指示的业务类型同步消息的报文格式可以如下表3所示，其中，业务流指示以五元组为例：
表3
Figure PCTCN2021098388-appb-000001
其中各字段的含义如下：
边缘设备地址：4字节，表示边缘设备的互联网协议(IP，Internet Protocol)地址；
核心设备地址：4字节，标识核心设备的IP地址；
Type：2字节，设定值为1表示该报文用于业务类型同步；
Len：2字节，表示报文的总长度；
源地址：4字节，表示业务报文的源IP地址；
目的地址：4字节，表示业务报文的目的IP地址；
源端口号：4字节，表示业务报文源端的端口号；
目的端口号：4字节，表示业务报文目的端的端口号；
传输层协议号：4字节，表示传输层使用的协议的协议号；
Apptype：表示业务类型标识；
Action：设定值为1标识该报文用于添加策略，上述业务类型同步消息中该字段即为1。
下面对于核心设备对第二业务报文分配优先级的方法进行说明：
结合上述核心设备判断该第二业务报文与上述第一业务报文属于相同业务流的方法，核心设备在边缘设备发送的业务流指示和业务类型标识后，可以查询存储的业务优先级对应关系，获取业务类型标识对应的优先级的值。然后，可以在本地的业务流和优先级的对应关系中，添加上述业务流指示和优先级的值的对应关系。业务流和优先级的对应关系可以如下表4所示：
表4
业务流指示 优先级的值
a 1
b 2
c 3
…… ……
核心设备在确定第二业务报文的业务流指示后，可以在业务流和优先级的对应关系中查询该第二业务报文的业务流指示对应的优先级的值。查询到的第二业务报文的业务流指示对应的优先级的值所标识的优先级即为分配给第二业务报文的优先级。
因为第二业务报文和第一业务报文属于相同业务流，则第二业务报文对应的优先级与上述第一业务对应的优先级相同。
在一种可能的实现方式中，核心设备在转发第二业务报文之前，可以将将第二业务报文中的优先级字段的值设置为指示优先级的值。这里的设置可以包括修改或添加。这样，边缘设备在接收到第二业务报文后，可以根据其中携带的优先级的所标识的优先级向终端转发该第二业务报文。
相应的，边缘设备如果接收来自核心设备的第二业务报文中的优先级字段的值属于免识别集合，则忽略识别第二业务报文的业务类型，直接通过该优先级字段的值所标识的优先级转发该第二报文。此处，由于在未分配优先级的情况下，业务报文的优先级字段的值通常为固定值，如果在第二业务报文中优先级字段中的值为免识别集合中值，则说明有与该第二业务报文属于相同业务流的报文被识别业务类型。免识别集合可以为除上述固定值以外的其余优先级的值所组成的集合。
在一种可能的实现方式中，核心设备可以对存储的业务流和优先级的对应关系中的部分信息进行删除，以节省存储资源。相应的，可以如下两种删除机制：
机制一、核心设备如果在最近一次接收到业务流指示为目标业务流指示的业务报文后的预设时长内，未接收到业务流指示为目标业务流指示的业务报文，则删除目标业务流指示和优先级的值的对应关系。此机制下，可以由核心设备自行实现对业务流和优先级的对应关系中的部分信息进行删除，无需与其余网络设备交互，可以节省数据传输资源。其中，预设时长可以根据实际需求设置，如1分钟、5分钟等。
机制二、边缘设备如果在最近一次接收到业务流指示为目标业务流指示的业务报文后的预设时长内，未接收到业务流指示为目标业务流指示的业务报文，则向核心设备发删除消息，其中，删除消息携带目标业务流指示。核心设备则根据删除消息，删除目标业务流指示和优先级的值的对应关系。此机制下，判断对哪些信息进行删除由闲置计算资源相对较多接入设备实现，而核心设备只需要在接收到策略删除消息后，执行相应的删除操作即可，可以节省核心设备的计算资源。其中，预设时长可以根据实际需求设置，如1分钟、5分钟等。
在上述机制二中，边缘设备向核心设备发送的删除消息的报文格式和上述表3所示的报文格式可以相同，只需将其中的Action字段的设定值填为0，其余字段按实际情况添加即可。当然，该删除消息的报文格式也在上述表3所示的报文格式的基础上删除Apptype字段，将其中的Action字段的设定值填为0，其余字段按实际情况添加。删除Apptype字段后删除消息的报文格式可以如下表5所示：
表5
Figure PCTCN2021098388-appb-000002
需要说明的是，该表5中各字段的含义与上述表3中各字段的含义相同，在此不再赘述。
在本申请实施例中，由边缘设备识别某业务流的业务报文的业务类型，并将该业务流对应的业务类型上报至核心设备。由于每个边缘设备所连接的终端数量相对较少，那么，边缘设备就可以有足够的硬件资源实现对业务类型的精细识别。核心设备在转发该会话的其他业务报文时，无需对其进行业务类型识别，只需对其分配优先级并转发即可。综上，在本申请中，对业务类型的识别和优先级分配放在不同设备中实现，可以实现对业务报文的业务类型进行精细识别，并分配对应的优先级，则不会出现不同业务的业务报文被识别为相同业务类型，可以有效减少由于不同业务的业务报文被识别为相同业务类型而造成的拥塞、丢包等问题。
参见图3，本申请实施例提供了还一种数据传输的方法，该方法的处理流程可以包括如下步骤：
步骤301、边缘设备接收来自核心设备的第一业务报文。
步骤302、边缘设备识别第一业务报文中的第一业务报文的目标业务类型，并提取第一业务报文中的目标业务流指示。
步骤303、边缘设备向核心设备发送业务类型同步消息。
其中，业务类型同步消息中携带目标业务类型标识和目标业务流指示，目标业务类型标识用于标识目标业务类型。
步骤304、核心设备根据业务优先级对应关系，确定目标业务类型对应的目标优先级，建立目标业务流指示和目标优先级的对应关系。
步骤305、核心设备接收第二业务报文。
步骤306、核心设备提取第二业务报文中的业务流指示，确定第二业务报文中的业务流指示为目标业务流指示，获取目标业务流指示对应的目标优先级的值，在第二业务报文中设置目标优先级的值。
步骤307、核心设备根据目标优先级向边缘设备转发携带目标优先级的值的第二业务报文。
步骤308、边缘设备确定第二业务报文中的优先级字段的值属于免识别集合，忽略识别第二业务报文的业务类型，并根据目标优先级向终端转发第二业务报文。
步骤309、边缘设备如果在预设时长内未接收到业务流指示为目标业务流指示的业务报文，则向核心设备发送删除消息。
其中，删除消息携带目标业务流指示。
步骤310、核心设备根据删除消息，删除目标优先级和目标业务流指示的对应关系。
需要说明的是，图3所示的方法流程中边缘设备和核心设备所执行操作的具体实施方式，与上述图2所示的方法流程中边缘设备和核心设备所执行操作的具体实施方式相同，在此不再赘述。
在本申请实施例中，由边缘设备识别某业务流的业务报文的业务类型，并将该业务流对应的业务类型上报至核心设备。由于每个边缘设备所连接的终端数量相对较少，那么，边缘设备就可以有足够的硬件资源实现对业务类型的精细识别。核心设备在转发该会话的其他业务报文时，无需对其进行业务类型识别，只需对其分配优先级并转发即可。综上，在本申请中，对业务类型的识别和优先级分配放在不同设备中实现，可以实现对业务报文的业务类型进行精细识别，并分配对应的优先级，则不会出现不同业务的业务报文被识别为相同业务类型，可以有效减少由于不同业务的业务报文被识别为相同业务类型而造成的拥塞、丢包等问题。
基于相同的技术构思，本申请实施例还提供了一种数据传输的装置，该装置应用于网络中的边缘设备，网络包括核心设备和边缘设备，如图4所示，该装置包括：
识别模块410，用于识别来自所述核心设备的第一业务报文的业务类型。具体可以实现上述步骤201中提到的识别功能，以及其他隐含步骤。
发送模块420，用于向所述核心设备发送业务类型标识，所述业务类型标识用于标识所述业务类型，以使所述核心设备根据存储的业务优先级对应关系，确定所述业务类型标识对应的优先级，并根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。具体可以实现上述步骤201提到的发送功能，以及其他隐含步骤。
在一种可能的实现方式中，发送模块420，还用于如果在预设时长内未接收到属于所述业务流的业务报文，则向所述核心设备发送删除消息，其中，所述删除消息携带业务流指示。
在一种可能的实现方式中，该装置还包括：
接收模块，用于如果接收来自所述核心设备的所述第二业务报文中包括优先级字段，则 忽略识别所述第二业务报文的业务类型，或者，如果接收来自所述核心设备的所述第二业务报文中的优先级字段的值属于免识别集合，忽略识别所述第二业务报文的业务类型。
在本申请实施例中，由边缘设备识别某业务流的业务报文的业务类型，并将该业务流对应的业务类型上报至核心设备。由于每个边缘设备所连接的终端数量相对较少，那么，边缘设备就可以有足够的硬件资源实现对业务类型的精细识别。核心设备在转发该会话的其他业务报文时，无需对其进行业务类型识别，只需对其分配优先级并转发即可。综上，在本申请中，对业务类型的识别和优先级分配放在不同设备中实现，可以实现对业务报文的业务类型进行精细识别，并分配对应的优先级，则不会出现不同业务的业务报文被识别为相同业务类型，可以有效减少由于不同业务的业务报文被识别为相同业务类型而造成的拥塞、丢包等问题。
需要说明的是：上述实施例提供的数据传输的装置在进行数据传输时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将边缘设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的数据传输的装置与数据传输的方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
基于相同的技术构思，本申请实施例还提供了一种数据传输的装置，该装置应用于网络中的核心设备，网络包括核心设备和边缘设备，如图5所示，该装置包括：
接收模块510，用于接收来自所述边缘设备的业务类型标识，其中，所述业务类型标识用于标识所述边缘设备接收到的来自所述核心设备的第一业务报文的业务类型。具体可以实现上述步骤201提到的核心设备的接收功能，以及其他隐含步骤。
确定模块520，用于根据存储的所述业务优先级对应关系，确定所述业务类型标识对应的优先级，根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。具体可以实现上述步骤202提到的核心设备的确定功能，以及其他隐含步骤。
在一种可能的实现方式中，所述接收模块510，还用于：
接收来自所述边缘设备的所述第一业务报文所属业务流的业务流指示；
所述装置还包括：
建立模块，用于建立所述第一业务报文所属业务流和所述优先级的对应关系。
在一种可能的实现方式中，接收模块510还用于：
接收来自所述边缘设备的删除消息，其中，所述策略删除消息携带所述业务流指示，删除所述第一业务报文所属业务流和所述优先级的对应关系。
在一种可能的实现方式中，该装置还包括：
删除模块，用于如果在预设时长内未接收到属于所述业务流的业务报文，则删除所述业务流和所述优先级的对应关系。
在本申请实施例中，由边缘设备识别某业务流的业务报文的业务类型，并将该业务流对应的业务类型上报至核心设备。由于每个边缘设备所连接的终端数量相对较少，那么，边缘设备就可以有足够的硬件资源实现对业务类型的精细识别。核心设备在转发该会话的其他业务报文时，无需对其进行业务类型识别，只需对其分配优先级并转发即可。综上，在本申请 中，对业务类型的识别和优先级分配放在不同设备中实现，可以实现对业务报文的业务类型进行精细识别，并分配对应的优先级，则不会出现不同业务的业务报文被识别为相同业务类型，可以有效减少由于不同业务的业务报文被识别为相同业务类型而造成的拥塞、丢包等问题。
需要说明的是：上述实施例提供的数据传输的装置在进行数据传输时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将核心设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的数据传输的装置与数据传输的方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本申请实施例还提供了一种边缘设备，如图6所示该边缘设备600，包括处理器601、存储器602、通信接口603和总线604。处理器601、存储器602和通信接口603通过总线604彼此通信连接。本领域技术人员应当明白，图6所示的处理器601、存储器602和通信接口603之间的连接方式仅仅是示例性的，在实现过程中，处理器601、存储器602和通信接口603也可以采用除了总线604之外的其他连接方式彼此通信连接。
其中，存储器602用于存储指令6021和数据6022。存储器602可以是各种类型的存储介质，例如存储器602可以是随机存取存储器(random access memory，RAM)、只读存储器(read-only memory，ROM)、非易失性RAM(non-volatile RAM，NVRAM)、可编程ROM(programmable ROM，PROM)、可擦除PROM(erasable PROM，EPROM)、电可擦除PROM(electrically erasable PROM，EEPROM)、闪存、光存储器和寄存器等。并且，该存储器602可以包括硬盘和/或内存。
其中，处理器601可以是通用处理器，通用处理器可以是通过读取并执行存储器(例如存储器602)中存储的指令(例如指令6021)来执行特定步骤和/或操作的处理器，通用处理器在执行上述步骤和/或操作的过程中可能用到存储在存储器(例如存储器602)中的数据(例如数据6022)。通用处理器可以是，例如但不限于，中央处理器(central processing unit，CPU)。此外，处理器601也可以是专用处理器，专用处理器可以是专门设计的用于执行特定步骤和/或操作的处理器，该专用处理器可以是，例如但不限于，数字信号处理器(digital signal processor，DSP)、应用专用集成电路(application-specific integrated circuit，ASIC)和现场可编程门阵列(field-programmable gate array，FPGA)等。此外，处理器601还可以是多个处理器的组合，例如多核处理器。处理器601可以包括一个或多个电路，以执行上述实施例提供的数据传输的方法的全部或部分步骤。
其中，通信接口603可以包括输入/输出(input/output，I/O)接口、物理接口和逻辑接口等用于实现边缘设备600内部的器件互连的接口，以及用于实现边缘设备600与其他设备(例如网络设备或工作站)互连的接口。物理接口可以是千兆的以太接口(gigabit ethernet，GE)，其可以用于实现边缘设备600与其他设备(例如网络设备或工作站)互连，逻辑接口是边缘设备600内部的接口，其可以用于实现边缘设备600内部的器件互连。容易理解，通信接口603可以用于边缘设备600与其他网络设备和/或工作站通信，例如，通信接口603用于边缘设备600与其他网络设备之间消息的发送和接收。
其中，总线604可以是任何类型的，用于实现处理器601、存储器602和通信接口603 互连的通信总线，例如系统总线。
上述器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的需要。本申请实施例对上述器件的具体实现形式不做限定。
本申请实施例还提供了一种核心设备，如图7所示该核心设备700，包括处理器701、存储器702、通信接口703和总线704。处理器701、存储器702和通信接口703通过总线704彼此通信连接。本领域技术人员应当明白，图7所示的处理器701、存储器702和通信接口703之间的连接方式仅仅是示例性的，在实现过程中，处理器701、存储器702和通信接口703也可以采用除了总线704之外的其他连接方式彼此通信连接。
其中，存储器702用于存储指令7021和数据7022。存储器702可以是各种类型的存储介质，例如存储器702可以是随机存取存储器(random access memory，RAM)、只读存储器(read-only memory，ROM)、非易失性RAM(non-volatile RAM，NVRAM)、可编程ROM(programmable ROM，PROM)、可擦除PROM(erasable PROM，EPROM)、电可擦除PROM(electrically erasable PROM，EEPROM)、闪存、光存储器和寄存器等。并且，该存储器702可以包括硬盘和/或内存。
其中，处理器701可以是通用处理器，通用处理器可以是通过读取并执行存储器(例如存储器702)中存储的指令(例如指令7021)来执行特定步骤和/或操作的处理器，通用处理器在执行上述步骤和/或操作的过程中可能用到存储在存储器(例如存储器702)中的数据(例如数据7022)。通用处理器可以是，例如但不限于，中央处理器(central processing unit，CPU)。此外，处理器701也可以是专用处理器，专用处理器可以是专门设计的用于执行特定步骤和/或操作的处理器，该专用处理器可以是，例如但不限于，数字信号处理器(digital signal processor，DSP)、应用专用集成电路(application-specific integrated circuit，ASIC)和现场可编程门阵列(field-programmable gate array，FPGA)等。此外，处理器701还可以是多个处理器的组合，例如多核处理器。处理器701可以包括一个或多个电路，以执行上述实施例提供的数据传输的方法的全部或部分步骤。
其中，通信接口703可以包括输入/输出(input/output，I/O)接口、物理接口和逻辑接口等用于实现核心设备700内部的器件互连的接口，以及用于实现核心设备700与其他设备(例如网络设备或工作站)互连的接口。物理接口可以是千兆的以太接口(gigabit ethernet，GE)，其可以用于实现核心设备700与其他设备(例如网络设备或工作站)互连，逻辑接口是核心设备700内部的接口，其可以用于实现核心设备700内部的器件互连。容易理解，通信接口703可以用于核心设备700与其他网络设备和/或工作站通信，例如，通信接口703用于核心设备700与其他网络设备之间消息的发送和接收。
其中，总线704可以是任何类型的，用于实现处理器701、存储器702和通信接口703互连的通信总线，例如系统总线。
上述器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的需要。本申请实施例对上述器件的具体实现形式不做限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现，当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令，在设备上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴光缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是设备能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(如软盘、硬盘和磁带等)，也可以是光介质(如数字视盘(Digital Video Disk，DVD)等)，或者半导体介质(如固态硬盘等)。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本申请一个实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (28)

  1. 一种网络，其特征在于，所述网络包括核心设备和边缘设备，其中，
    所述边缘设备，用于识别来自所述核心设备的第一业务报文的业务类型，并向所述核心设备发送业务类型标识，所述业务类型标识用于标识所述业务类型；
    所述核心设备，用于存储业务优先级对应关系，根据所述业务优先级对应关系，确定所述业务类型标识对应的优先级，并根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
  2. 根据权利要求1所述的网络，其特征在于，所述边缘设备，还用于发送所述第一业务报文所属业务流的业务流指示。
  3. 根据权利要求1或2所述的网络，其特征在于，所述核心设备，还用于建立所述第一业务报文所属业务流和所述优先级的对应关系。
  4. 根据权利要求3所述的网络，其特征在于，所述边缘设备，还用于：
    如果在预设时长内未接收到属于所述业务流的业务报文，则向所述核心设备发送删除消息，其中，所述删除消息携带业务流指示。
  5. 根据权利要求4所述的网络，其特征在于，所述核心设备，还用于根据所述删除消息，删除所述业务流和所述优先级的对应关系。
  6. 根据权利要求3所述的网络，其特征在于，所述核心设备，还用于：
    如果在预设时长内未接收到属于所述业务流的业务报文，则删除所述业务流和所述优先级的对应关系。
  7. 根据权利要求1-6中任一项所述的网络，其特征在于，所述核心设备，还用于：
    将所述第二业务报文中的优先级字段的值设置为指示所述优先级的值。
  8. 根据权利要求7所述的网络，其特征在于，所述边缘设备，还用于：
    如果接收来自所述核心设备的上述第二业务报文中包括优先级字段，则忽略识别所述第二业务报文的业务类型。
  9. 根据权利要求1-6中任一项所述的网络，其特征在于，所述边缘设备，还用于：
    如果接收来自所述核心设备的所述第二业务报文中的优先级字段的值属于免识别集合，忽略识别所述第二业务报文的业务类型。
  10. 根据权利要求1-9中任一项所述的网络，其特征在于，所述网络为叠加网络。
  11. 根据权利要求1-10中任一项所述的网络，其特征在于，所述网络为园区网络。
  12. 一种数据传输的方法，其特征在于，所述方法应用于网络中的边缘设备，所述网络包括核心设备和边缘设备，所述方法包括：
    所述边缘设备识别来自所述核心设备的第一业务报文的业务类型，并向所述核心设备发送业务类型标识，所述业务类型标识用于标识所述业务类型，以使所述核心设备根据存储的业务优先级对应关系，确定所述业务类型标识对应的优先级，并根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述边缘设备如果在预设时长内未接收到属于所述业务流的业务报文，则向所述核心设备发送删除消息，其中，所述删除消息携带业务流指示。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述边缘设备如果接收来自所述核心设备的所述第二业务报文中包括优先级字段，则忽略识别所述第二业务报文的业务类型，或者，如果接收来自所述核心设备的所述第二业务报文中的优先级字段的值属于免识别集合，忽略识别所述第二业务报文的业务类型。
  15. 一种数据传输的方法，其特征在于，所述方法应用于网络中的核心设备，所述叠加网络包括所述核心设备和边缘设备，所述方法包括：
    所述核心设备接收来自所述边缘设备的业务类型标识，其中，所述业务类型标识用于标识所述边缘设备接收到的来自所述核心设备的第一业务报文的业务类型；
    所述核心设备根据存储的所述业务优先级对应关系，确定所述业务类型标识对应的优先级，根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述核心设备接收来自所述边缘设备的所述第一业务报文所属业务流的业务流指示；
    所述核心设备建立所述第一业务报文所属业务流和所述优先级的对应关系。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述核心设备接收来自所述边缘设备的删除消息，其中，所述策略删除消息携带所述业务流指示；
    所述核心设备删除所述第一业务报文所属业务流和所述优先级的对应关系。
  18. 根据权利要求15或16所述的方法，其特征在于，所述方法还包括：
    所述核心设备如果在预设时长内未接收到属于所述业务流的业务报文，则删除所述业务流和所述优先级的对应关系。
  19. 一种数据传输的装置，其特征在于，所述装置应用于网络中的边缘设备，所述网络包括核心设备和边缘设备，所述装置包括：
    识别模块，用于识别来自所述核心设备的第一业务报文的业务类型；
    发送模块，用于向所述核心设备发送业务类型标识，所述业务类型标识用于标识所述业务类型，以使所述核心设备根据存储的业务优先级对应关系，确定所述业务类型标识对应的优先级，并根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
  20. 根据权利要求19所述的装置，其特征在于，所述发送模块还用于：
    如果在预设时长内未接收到属于所述业务流的业务报文，则向所述核心设备发送删除消息，其中，所述删除消息携带业务流指示。
  21. 根据权利要求19或20所述的装置，其特征在于，所述装置还包括：
    接收模块，用于如果接收来自所述核心设备的所述第二业务报文中包括优先级字段，则忽略识别所述第二业务报文的业务类型，或者，如果接收来自所述核心设备的所述第二业务报文中的优先级字段的值属于免识别集合，忽略识别所述第二业务报文的业务类型。
  22. 一种数据传输的装置，其特征在于，所述装置应用于网络中的核心设备，所述网络包括所述核心设备和边缘设备，所述装置包括：
    接收模块，用于接收来自所述边缘设备的业务类型标识，其中，所述业务类型标识用于标识所述边缘设备接收到的来自所述核心设备的第一业务报文的业务类型；
    确定模块，用于根据存储的所述业务优先级对应关系，确定所述业务类型标识对应的优先级，根据所述优先级转发第二业务报文，其中，所述第二业务报文和所述第一业务报文属于相同业务流，所述业务优先级对应关系包括多种业务类型到多个优先级的映射。
  23. 根据权利要求22所述的装置，其特征在于，所述接收模块，还用于：
    接收来自所述边缘设备的所述第一业务报文所属业务流的业务流指示；
    所述装置还包括：
    建立模块，用于建立所述第一业务报文所属业务流和所述优先级的对应关系。
  24. 根据权利要求23所述的装置，其特征在于，所述接收模块还用于：
    接收来自所述边缘设备的删除消息，其中，所述策略删除消息携带所述业务流指示，删除所述第一业务报文所属业务流和所述优先级的对应关系。
  25. 根据权利要求22或23所述的装置，其特征在于，所述装置还包括：
    删除模块，用于如果在预设时长内未接收到属于所述业务流的业务报文，则删除所述业 务流和所述优先级的对应关系。
  26. 一种边缘设备，其特征在于，所述边缘设备包括：处理器和存储器，所述存储器中存储有程序，所述处理器用于调用所述存储器中存储的程序，使得所述边缘设备执行如权利要求12至14中任一所述的数据传输的方法。
  27. 一种核心设备，其特征在于，所述核心设备包括：处理器和存储器，所述存储器中存储有程序，所述处理器用于调用所述存储器中存储的程序，使得所述核心设备执行如权利要求15至18中任一所述的数据传输的方法。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序在网络设备上运行时，使得所述网络设备执行如权利要求12-18中任一所述的网络配置的方法。
PCT/CN2021/098388 2020-06-30 2021-06-04 网络、数据传输的方法和装置 Ceased WO2022001581A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21832855.7A EP4156563A4 (en) 2020-06-30 2021-06-04 NETWORK, AND DATA TRANSMISSION METHOD AND APPARATUS
US18/148,914 US20230148392A1 (en) 2020-06-30 2022-12-30 Network and data transmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010615469.1 2020-06-30
CN202010615469.1A CN113872880B (zh) 2020-06-30 2020-06-30 网络、数据传输的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/148,914 Continuation US20230148392A1 (en) 2020-06-30 2022-12-30 Network and data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2022001581A1 true WO2022001581A1 (zh) 2022-01-06

Family

ID=78981482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/098388 Ceased WO2022001581A1 (zh) 2020-06-30 2021-06-04 网络、数据传输的方法和装置

Country Status (4)

Country Link
US (1) US20230148392A1 (zh)
EP (1) EP4156563A4 (zh)
CN (1) CN113872880B (zh)
WO (1) WO2022001581A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115695329A (zh) * 2022-10-21 2023-02-03 中国电力科学研究院有限公司 变电站业务数据确定性传输方法和系统及网络交换机
US20250150455A1 (en) * 2023-11-06 2025-05-08 Zscaler, Inc. Systems and methods for generating sub-identities for workloads

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6970478B1 (en) * 1999-06-01 2005-11-29 Nec Corporation Packet transfer method and apparatus, and packet communication system
CN101594289A (zh) * 2008-05-28 2009-12-02 华为技术有限公司 实现区分服务流量工程的方法及设备
CN102025620A (zh) * 2010-12-07 2011-04-20 南京邮电大学 基于业务区分的认知网络QoS保障方法
CN103701710A (zh) * 2013-12-20 2014-04-02 杭州华为数字技术有限公司 一种数据传输方法、核心转发设备以及端点转发设备
CN109743316A (zh) * 2018-12-29 2019-05-10 中国联合网络通信集团有限公司 数据传输方法、出口路由器、防火墙及双台防火墙系统
CN110740481A (zh) * 2018-07-18 2020-01-31 中国移动通信有限公司研究院 基于服务质量的数据处理方法、设备和计算机存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1294728C (zh) * 2004-08-05 2007-01-10 华为技术有限公司 边缘路由器提供服务质量保证的方法及系统
CN102143035B (zh) * 2010-06-04 2013-06-12 华为技术有限公司 数据业务处理方法、网络设备和网络系统
CN107733799B (zh) * 2016-08-11 2021-09-21 新华三技术有限公司 一种报文传输方法和装置
CN108566341B (zh) * 2018-04-08 2021-01-15 西安交通大学 一种sd-wan环境中流量控制方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6970478B1 (en) * 1999-06-01 2005-11-29 Nec Corporation Packet transfer method and apparatus, and packet communication system
CN101594289A (zh) * 2008-05-28 2009-12-02 华为技术有限公司 实现区分服务流量工程的方法及设备
CN102025620A (zh) * 2010-12-07 2011-04-20 南京邮电大学 基于业务区分的认知网络QoS保障方法
CN103701710A (zh) * 2013-12-20 2014-04-02 杭州华为数字技术有限公司 一种数据传输方法、核心转发设备以及端点转发设备
CN110740481A (zh) * 2018-07-18 2020-01-31 中国移动通信有限公司研究院 基于服务质量的数据处理方法、设备和计算机存储介质
CN109743316A (zh) * 2018-12-29 2019-05-10 中国联合网络通信集团有限公司 数据传输方法、出口路由器、防火墙及双台防火墙系统

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN113872880A (zh) 2021-12-31
EP4156563A1 (en) 2023-03-29
EP4156563A4 (en) 2023-11-01
CN113872880B (zh) 2024-04-16
US20230148392A1 (en) 2023-05-11

Similar Documents

Publication Publication Date Title
US10659342B2 (en) Flow entry configuration method, apparatus, and system
KR102579059B1 (ko) 패킷 처리 방법 및 장치, 기기, 그리고 시스템
CN105099789B (zh) 一种网元升级方法及设备
JP2023126364A (ja) スライスベースネットワークにおける輻輳回避
CN105577540B (zh) 一种业务链路的建立方法、装置及系统
CN110278152B (zh) 一种建立快速转发表的方法及装置
CN106357542B (zh) 提供组播业务的方法和软件定义网络控制器
CN110944039B (zh) 面向5g接入网的微服务发现方法、系统及装置
WO2021098425A1 (zh) 配置业务的服务质量策略方法、装置和计算设备
WO2020155941A1 (zh) 一种报文调度方法、相关设备及计算机存储介质
WO2022253194A1 (zh) 报文转发方法、装置及通信网络
WO2022253190A1 (zh) 业务流的性能检测方法、装置及通信网络
US20230148392A1 (en) Network and data transmission method and apparatus
CN113162855B (zh) 组播报文检测方法、网络设备和系统
RU2687215C1 (ru) Способ и устройство для передачи информации о функциях коммутатора openflow
CN113395612B (zh) 一种光纤通信中的数据转发方法以及相关装置
WO2023109672A1 (zh) 业务处理方法、装置及系统
WO2022253192A1 (zh) 报文转发方法、装置及通信网络
US11153214B2 (en) In service flow capability update in guaranteed bandwidth multicast network
CN113872783B (zh) 网络配置的方法、装置及计算机可读存储介质
CN117081967A (zh) 传输检测方法、装置及系统
WO2022160876A1 (zh) 一种接入用户设备的接口管理方法及接入用户设备
US11902087B2 (en) Forwarding fault location determining method and device
CN104243361B (zh) 一种业务处理的方法及系统
WO2025086632A1 (zh) 一种基于物联网技术的消息传输配置方法、装置、设备及介质

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021832855

Country of ref document: EP

Effective date: 20221221

NENP Non-entry into the national phase

Ref country code: DE