WO2021043232A1 - 主机网络性能需求可编程化的方法、设备和系统 - Google Patents

主机网络性能需求可编程化的方法、设备和系统 Download PDF

Info

Publication number
WO2021043232A1
WO2021043232A1 PCT/CN2020/113363 CN2020113363W WO2021043232A1 WO 2021043232 A1 WO2021043232 A1 WO 2021043232A1 CN 2020113363 W CN2020113363 W CN 2020113363W WO 2021043232 A1 WO2021043232 A1 WO 2021043232A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
service message
network device
host
network
Prior art date
Application number
PCT/CN2020/113363
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 EP20860842.2A priority Critical patent/EP4024782A4/en
Publication of WO2021043232A1 publication Critical patent/WO2021043232A1/zh
Priority to US17/686,983 priority patent/US20220191138A1/en

Links

Images

Classifications

    • 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/34—Source 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/70—Routing based on monitoring results
    • 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
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • This application relates to the field of communications, and in particular to a method, device, and system for programmability of host network performance requirements in a segment routing (SR) network.
  • SR segment routing
  • SR is a protocol designed based on the concept of source routing to forward data packets on the network. It supports the explicit designation of the data packet forwarding path on the source network device.
  • This application provides a method, device and system for sending a message, and a host that supports sending a message directly proposes a programmable network performance requirement to the SR network, so as to solve the technical problem that the configured network performance requirement is not flexible enough.
  • this application provides a method for sending messages.
  • the network device receives a first service message from the host, the first service message includes a first identifier, and the first identifier indicates the network performance requirement of the first service message;
  • a segment list is added to the first service message to obtain a second service message, wherein the element includes the first identifier, and the forwarding path corresponding to the segment list meets the network performance requirement; the network device Forward the second service packet through the forwarding path.
  • This method can be executed by the gateway device of the SR network.
  • the gateway device directly receives the network performance requirements proposed by the host, making the way of acquiring the network performance requirements more flexible, and the gateway device uses the network performance requirements proposed by the host as an element for determining the forwarding path of service packets, thereby improving network efficiency.
  • the method before the network device receives the first service message from the host, the method further includes: the network device sends a control message to the host, and the control The message includes a second identifier; wherein, the first service message includes a first segment identifier, the first segment identifier includes a location field and a function field, the location field includes the address of the network device, and the function The field includes the first identification and the second identification.
  • the network device obtains the type value corresponding to the function of receiving the network performance requirement from the control message from the host, and carries the first identifier representing the network performance requirement in the service message in the form of a parameter of the function.
  • the element further includes the destination address of the first service message.
  • the value of the first identifier represents a color based on a service level agreement requirement.
  • this application provides a method for proposing network performance requirements.
  • the host sends a first service message to the network device, where the first service message includes a first identifier, and the first identifier indicates a network performance requirement of the first service message.
  • the method can be executed by the host, and the network performance requirement is added to the service message and then sent to the gateway device.
  • the host directly proposes the network performance requirement in a more flexible manner.
  • the method before the host sends the first service message to the network device, the method further includes: the host receives a control message from the network device, and the control The message includes a second identifier; wherein, the first service message includes a first segment identifier, the first segment identifier includes a location field and a function field, the location field includes the address of the network device, and the function The field includes the first identification and the second identification.
  • the host runs a first application and a second application, the first application is different from the second application, and the first service message is the first application
  • the second service packet is a service packet of the second application program
  • the method further includes: the host sends the second service packet to the network device, and the second service packet is
  • the service message includes a third identifier, the third identifier indicates the network performance requirement of the second service message, and the third identifier is different from the first identifier.
  • this application provides a network device that executes the first aspect or any one of the possible implementation methods of the first aspect.
  • the network device includes a unit for executing the method in the first aspect or any one of the possible implementation manners of the first aspect.
  • this application provides a host that executes the second aspect or any one of the possible implementation methods of the second aspect.
  • the host includes a unit for executing the second aspect or any one of the possible implementation manners of the second aspect.
  • this application provides a network device, which includes a processor, a network interface, and a memory.
  • the network interface can be a transceiver.
  • the memory may be used to store program code, and the processor is used to call the program code in the memory to execute the foregoing first aspect or any one of the possible implementation manners of the first aspect, which will not be repeated here.
  • the present application provides a host, which includes a processor, a network interface, and a memory.
  • the network interface can be a transceiver.
  • the memory may be used to store program code, and the processor is used to call the program code in the memory to execute the foregoing second aspect or any one of the possible implementation manners of the second aspect, which will not be repeated here.
  • the present application provides a network system that includes the network device provided in the foregoing third aspect and the host provided in the fourth aspect, or the network system includes the network device provided in the foregoing fifth aspect and the sixth aspect Host provided.
  • the present application provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause the computer to execute the methods described in the foregoing aspects.
  • this application provides a computer program product including computer program instructions, which when the computer program product runs on a network device, enables the network device to execute any one of the first aspect and the first aspect of the second aspect. Or the method provided in any one of the possible implementations of the second aspect.
  • this application provides a chip including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory to execute the first aspect and any of the first aspects.
  • the method in a possible implementation manner, or the processor executes the second aspect or the method in any possible implementation manner of the second aspect.
  • the aforementioned chip only includes a processor, and the processor is used to read and execute a computer program stored in the memory.
  • the processor executes the first aspect or any possible implementation method of the first aspect.
  • the processor executes the second aspect or any possible implementation manner of the second aspect.
  • Fig. 1 is a schematic diagram of a network scenario provided by an embodiment of the present invention.
  • Fig. 2 is a method for sending a message according to an embodiment of the present invention.
  • Fig. 3 is a format of an RA message provided by an embodiment of the present invention.
  • FIG. 4 is a structure of a segment identifier provided by an embodiment of the present invention.
  • Fig. 5 is a message header format provided by an embodiment of the present invention.
  • Fig. 6 is a schematic structural diagram of a network device provided by an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a network device provided by an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a network device provided by an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a network system provided by an embodiment of the present invention.
  • FIG. 1 shows a possible application scenario of an embodiment of the present invention.
  • This scenario includes an SR network, which includes several network devices, such as network device A, network device B, network device C, network device D, network device E, and network device F. These network devices may be routers, switches, or forwarders in a software-defined network (SDN) structure.
  • the network device A is the gateway of the host.
  • the gateway is used to transfer data packets between two networks. For example, two networks using different protocols can be connected together, and the data in the two network segments using different transmission protocols can be processed. Translation conversion.
  • the host connects to the SR network through network device A.
  • the network device A guides the traffic from the host to be forwarded through a specific forwarding path.
  • the host can be a terminal device, such as a personal computer, a mobile phone, or a tablet computer.
  • the host can also be a service providing computer, such as a server.
  • the embodiment of the present invention provides a method for sending a message and a device and system based on the method.
  • the method, equipment and system are based on the same inventive concept.
  • the principles of the method, device and system for solving the problem are similar. Therefore, the embodiments of the method, device and system can be referred to each other, and the same or similar parts will not be repeated.
  • an embodiment of the present invention provides a method for sending a message.
  • the gateway device of the SR network directly receives the network performance requirements proposed by the host, which makes the way of acquiring the network performance requirements more flexible.
  • the host 201 may be the host in FIG. 1
  • the network device 202 may be the gateway of the SR network, such as the network device A in FIG. 1.
  • the method includes:
  • the host 201 sends a service message to the network device 202, where the service message includes a first identifier, and the first identifier indicates a network performance requirement of the service message.
  • the service message may be a service message generated by the host 201.
  • the application program running on the host 201 generates the service message.
  • the host 201 may be a terminal device such as a personal computer, a mobile phone or a tablet computer, and the host 201 may run different application programs. These applications can respectively generate different business messages.
  • the host 201 runs application 1 and application 2, and application 1 and application 2 are different applications.
  • Application 1 generates business message 1, that is, business message 1 is a business message of application 1
  • application 2 generates business message 2 that is, business message 2 is a business message of application 2.
  • the service message may carry an identifier indicating the network performance requirement of the service message.
  • the network performance requirements of the service message may be Service Level Agreement (SLA) requirements, such as low latency, large bandwidth, short path hop count, and so on.
  • SLA Service Level Agreement
  • the value of the identifier carried in the service message may indicate the SLA requirement. For example, a mapping relationship can be established between each SLA requirement and each identification value, so that each identification value can be used to represent an SLA requirement.
  • the color attribute value required by the SLA may also be used as the identification value carried in the service message.
  • Each SLA requirement can be expressed as a color attribute, and each color attribute is mapped to a specific value. The corresponding relationship between the color attribute and the specific value is uniform across the network.
  • low-latency network performance requirements can be represented in green, and the corresponding value is 20.
  • the network performance requirement of large bandwidth can be expressed in blue, and the corresponding value is 40.
  • the value of the identifier carried in the service message may be a specific value of the above-mentioned color attribute mapping, for example, 20.
  • the network performance requirement may also be a network performance parameter value, and the value of the identifier carried in the service message is the parameter value. For example, if the network performance requirement is that the end-to-end delay limit is 10ms, the value of the identifier carried in the service message can be 10; if the network performance requirement is a bandwidth of 100M, the value of the identifier carried in the service message can be 100 .
  • the value of the identifier carried in the service message is an identifier of a message forwarding path that meets network performance requirements.
  • the packet forwarding path that meets the network performance requirement is the first path
  • the identifier of the first path in the network is path A
  • the value of the identifier carried in the service packet may be A.
  • the service message may include multiple network performance requirements at the same time.
  • different service messages can carry different identities, and business messages of different applications can also carry different identities.
  • the service message 1 generated by the application 1 includes the first identifier, and the value of the first identifier is 20, which represents the green color attribute, that is, the network performance requirement of the service message 1 is low latency
  • the service generated by the application 2 includes a second identifier, and the value of the second identifier is 40, which represents a blue color attribute, that is, the network performance requirement of the service message 2 is a large bandwidth. Therefore, by carrying the identifier representing the network performance requirement in the service message, the host 201 can directly propose its own network performance requirement, which is more flexible.
  • different network performance requirements can be proposed for different service messages, or different network performance requirements can be proposed based on different applications.
  • the network device 202 sends a control packet to the host 201 for notifying the host 201 that it can raise its own network performance requirements.
  • the control message may be a router advertisement (RA) message in the Neighbor Discovery Protocol (NDP).
  • RA router advertisement
  • NDP Neighbor Discovery Protocol
  • the RA message is sent by the gateway to the host periodically, or sent in response to a router solicitation (router solicitation) message of the host, and is used to notify the host of related information of the gateway.
  • the host 201 is the host shown in FIG. 1
  • the network device 202 is the gateway of the host, that is, the network device A.
  • the network device A sends an RA message to the host to notify the relevant information of the gateway.
  • Figure 3 shows the format of the RA message.
  • the RA message includes: Type field, Code field, Checksum field, Cur Hop Limit field, M flag bit, O flag, reserved (Reserved) field, router Lifetime field, Reachable Time field, Retrans Timer field, and Options field.
  • Network device A can extend the RA message.
  • network device A may set an enable flag in the option field, and the enable flag may be a type field with a specific value.
  • network device A can add an option with a type value of 38 as an enable flag in the option field.
  • the host receives the RA message, it reads an option with a type value of 38 in the option field, that is, it knows that it can carry the first identifier in the service message sent to network device A, thereby proposing its own network performance requirements .
  • the network device 202 may also notify the host 201 of the SRv6 network function of receiving network performance requirements through the control message. In the service message generated by the host 201, the network performance requirement is taken as the all The parameters of the function are carried. Furthermore, when the service message is sent from the host 201 to the network device 202, the network device 202 can receive and process the network performance requirements in the service message through the function.
  • the SRv6 network has a variety of functions. Each function includes corresponding operation steps to implement specific functions. Related parameters may be involved in the operation steps of the function. Each function can be represented by a function field of a specific value included in the SID.
  • Each parameter can also be represented by a parameter field of a specific numerical value included in the SID, and the parameter field representing the parameter is usually placed after the function field representing the function.
  • the type field representing the function may be followed by multiple different parameter fields representing different parameters.
  • the SID in the SRv6 network may include two parts: a location (Locator) field and a function (Function) field.
  • the location field includes a network device address prefix, which is used to locate a specific network device.
  • the function field includes the function (Function) of the SRv6 network implemented by the network device and the parameter (Argument) related to the function.
  • the parameter is optional.
  • the parameter field does not include the parameter.
  • the total length of the SID is 128 bits.
  • the location field and the function field are respectively specific lengths, and these specific lengths can be changed through network settings. For example, the location field is 64 bits, and the function field is 64 bits. Or, the location field is 48 bits, and the function field is 80 bits.
  • the network device queries the local SID table.
  • the local segment identification table includes the mapping relationship between the function and the function field of a specific value. The network device in the local segment identification table is based on the specific value.
  • the function field determines the function represented by the function field of the specific value.
  • the corresponding function can be determined according to the function field of the SID in the local segment identification table.
  • the function field entry representing the function of receiving network performance requirements is B112:0000:0000:0000
  • the function field carrying parameters is B112:0020:0000:0000.
  • the network device determines that the function represented by the function field is to receive network performance requirements, and according to the format of the function carrying parameters, identifies 0020 as a parameter, which represents a low-latency network performance requirement.
  • the function field of the SID can carry multiple parameters.
  • the function field carrying parameters can be B112:0020:0010:0100, and the network device determines that the function represented by the function field is to receive network performance requirements, and according to the format of the function carrying parameters, it recognizes that 0020, 0010 and 0100 are The parameters represent low latency, the upper limit of end-to-end latency is 10ms, and the bandwidth requirement is 100M.
  • the function for receiving network performance requirements may be a variation of the End.B6.Insert function, or the function for receiving network performance requirements may be a variation of the End.B6.Encaps function.
  • the control message sent by the network device 202 to the host 201 may include a second identifier, and the value of the second identifier may be a function field of a specific value corresponding to a function that receives network performance requirements.
  • the control message further includes a description field, which is used to describe the correspondence between the function for receiving network performance requirements and the function field of a specific value.
  • the description field may be a specific field in the RA message.
  • the description field may be the SRV6 node function (Endpoint Function) field in the RA message.
  • the host 201 generates a service message including the first identifier and the second identifier.
  • the second identifier and the first identifier may be included in the same SID of the service message, and the second identifier and the first identifier may be included in the function field of the SID,
  • the value of the second identifier is used to indicate a function of receiving network performance requirements
  • the value of the first identifier is used to indicate network performance requirements
  • the value of the first identifier is used as a parameter of the function.
  • the location field of the SID in the service message may include the address prefix of the network device 202, that is, the SID in the service message is the segment identifier of the network device 202.
  • the SID is the segment identifier of the network device 202, which means that the location field of the SID includes the address prefix of the network device 202.
  • the SID can be the node SID of the network device 202 or It is the adjacent class identifier (adjacent SID) of the link of the network device 202.
  • the second identifier may be included in the SID of the control message.
  • the second identifier may be included in the function field of the SID.
  • the location field of the SID in the control message may include the address prefix of the network device 202, that is, the SID in the control message is the segment identifier of the network device 202.
  • the network device A sends an RA message to the host, and the option field of the RA message includes an enable flag with a type value of 38.
  • the RA message also includes the segment identifier SID A1 of network device A.
  • SID A1 is 1111:0000:0000:0000:B112:0000:0000:0000/h
  • the length is 128 bits
  • "/h" means that the value is expressed in hexadecimal.
  • the first 64 bits are the location field, that is, 1111:0000:0000:0000, which matches the address prefix of network device A.
  • the last 64 bits are the function field, that is, B112:0000:0000:0000, including the second identifier B112:: where "::" represents all 0s, and the value of the second identifier represents the function of receiving network performance requirements.
  • the host receives the RA message sent by network device A, reads the enable flag with the type value of 38 in the RA message, and learns that it can directly put forward network performance requirements to network device A, that is, the service sent to network device A
  • the message carries the first identifier indicating the network performance requirement.
  • the host reads the second identifier B112:: in the RA message, and obtains the corresponding relationship between the value of the second identifier and the function of receiving network performance requirements in the SRV6Endpoint Function field of the RA message, and determines the second identifier
  • the indicated function is to receive network performance requirements.
  • the host generates a service message 1 including the first identifier and the second identifier.
  • the service message 1 may include the segment identifier SID A2 of the network device A, and the SID A2 is 1111:0000:0000:0000:B112:0020:0000:0000.
  • the function field is B112:0020:0000:0000, including the second identifier B112 and the first identifier 0020, where the value of the first identifier is 20/h, which indicates that the network performance requirement of the service packet 1 is low latency. Therefore, the host directly expresses its own network performance requirements by setting the first identifier in the service message 1.
  • segment routing header segment routing header
  • Figure 5 shows the format of the IPv6 message header and SRH.
  • IPv6 packet header includes: Version (Version) field, Traffic Class (Traffic Class) field, Flow Label (Flow Label) field, Payload Length (Payload Length) field, Next Header field, Hop Limit (Hop) Limit) field, Source Address (Source Address) field, Destination Address (Destination Address, DA) field.
  • SRH includes: Next Header field, Hdr Ext Len field, Routing Type field, Segment Left field, Last Entry field, Flag ( Flags) field, tag (Tag) field, segment list (Segment List) field, optional type length value object (Optional TLV objects) field.
  • the host 201 After the host 201 generates the service message, it encapsulates the segment list in the SRH of the service message, and sends the encapsulated service message.
  • the segment list includes a first segment identifier and a second segment identifier, and the first segment identifier may be the segment identifier of the network device 202.
  • the segment identifier of the network device 202 includes a location field and a function field
  • the location field includes the address prefix of the network device 202
  • the function field includes the second identifier and the first identifier.
  • the second segment identifier includes the destination address of the service message, and the destination address is the address prefix of the receiving device of the service message.
  • the host sends service message 1 to network device A
  • the destination address of service message 1 is receiving device X
  • service message 1 includes segment list 1, that is, SID list 1.
  • the SID list 1 includes two segment identifiers SID X and SID A2.
  • SIDA2 is the segment identifier of network device A
  • SID A2 can be 1111:0000:0000:0000:B112:0020:0000:0000, where the location field includes the address prefix of network device A, and the function field includes the second identifier and the first identifier .
  • SID X can be 1234:5678:0000:0000:0000:0000:0000, with a length of 128 bits, of which the first 64 bits are the location field, including the address prefix of the receiving device X, that is, 1234:5678:0000:0000/ 64 is also the destination address of service message 1.
  • SID X may also be a traditional IPv6 address, for example, 2001:0db8:85e3:0000:0000:8a2e:0370:7334.
  • the network device 202 receives the service message from the host 201, and adds a segment list to the service message according to the first identifier in the service message, and the forwarding path corresponding to the segment list satisfies the network of the service message. Performance requirements.
  • the network device 202 receives the service message from the host 201, adds a segment list to the service message, and then forwards the service message through the forwarding path corresponding to the segment list. In this process, the network device 202 adds a segment list to the service message according to the first identifier, and the forwarding path corresponding to the added segment list also meets the network performance requirements of the service message.
  • the network device 202 adds the segment list to the service message
  • the factor considered includes the destination address of the service message, that is, the network address in addition to the first identifier in the service message.
  • the device 202 adds a segment list to the service packet according to the destination address and the first identifier of the service packet.
  • the destination address of the service message is the address prefix of the receiving device of the service message.
  • network device A receives service message 1 sent by the host, the destination address of service message 1 is receiving device X, and service message 1 includes the first identifier, and the value of the first identifier It is 20, which represents the network performance requirement of low latency.
  • the network device A determines the segment list added to the service message 1 according to the destination address and the first identifier. For example, the network device A can obtain the mapping relationship between the combination of the destination address and the network performance requirement and the segment list, as shown in Table 1.
  • network device A Based on the destination address and the first identifier, network device A obtains the segment list from Table 1 as SID list 2, including SID B, SID D, SID E, and SID F, which are network device B, network device D, network device E, and The segment identifier of the network device F, that is, the forwarding path corresponding to the SID list 2 passes through the network device B, the network device D, and the network device E to the network device F. This is a forwarding path that meets the low-latency network performance requirements.
  • the network device A adds the SID list 2 to the service message 1, which is used to guide the forwarding of the service message 1. As a result, the service provided by the network can meet the network performance requirements directly proposed by the service message 1, and the method of proposing the network performance requirements is more flexible.
  • the network device 202 when the function field corresponding to the specific value of the function that receives the network performance requirement is carried in the service message, the network device 202 receives the network performance requirement proposed by the host 201 through this function, and according to the network performance requirement A segment list is added to the service message, and the forwarding path corresponding to the segment list meets the network performance requirements of the service message.
  • the network device A receives the service message 1 sent by the host, and processes the segment list in the SRH of the service message 1.
  • the segment list can be the above SID list 1, including SID X and SID A2, where SID X is the segment identifier of receiving device X, specifically 1234:5678:0000:0000:0000:0000, and SID A2 is the segment identifier of network device A, specifically 1111:0000:0000: 0000:B112:0020:0000:0000.
  • Network device A obtains SID A2 from the DA field, matches the 1111:0000:0000:0000:B112:0000:0000:0000 entry of the local local sid tab, determines the function field in it, that is, B112, and executes the function field. Representative function.
  • the specific process of network device A performing the function represented by the function field may include reading the parameter field behind the function field, and obtaining the value representing the network performance requirement in the parameter field, that is, the value 20; according to the updated SL in the segment list Find the final destination address of the service message, that is, the segment identifier SID X of the receiving device X. According to the value 20 and SID X, obtain the corresponding segment list from Table 1 above, namely SID list 2; add SID list 2 to the service report Text 1 is used to guide the forwarding of service message 1.
  • the function of receiving network performance requirements may be a variant of the End.B6.Insert function, and its specific execution process includes inserting the segment list as a new SRH header.
  • the function of receiving network performance requirements may be a variant of the End.B6.Encaps function, and its specific execution process includes encapsulating a new IPv6 header for the message, and inserting an SRH header carrying the segment list.
  • the network device 202 may receive different service messages, and the different service messages include different network performance requirements.
  • the network device 202 adds different segment lists for different service messages according to different network performance requirements, so that different service messages are sent out through a forwarding path that meets its network performance requirements.
  • the network device A receives the service message 1 and the service message 2 sent by the host, and the final destination addresses of the service message 1 and the service message 2 are both the receiving device X.
  • the service message 1 includes a first identifier, and the value of the first identifier is 20, which indicates a low-latency network performance requirement.
  • the service message 2 includes a third identifier, and the value of the third identifier is 40, which indicates a network performance requirement for a large bandwidth.
  • network device A can obtain the mapping relationship between different combinations of destination addresses and network performance requirements and different segment lists, as shown in Table 1. The network device A determines their forwarding path according to the destination address and network performance requirements in the service message 1 and the service message 2 respectively.
  • the segment list obtained by the network device A from Table 1 is the SID list 2, which is the same as the above-mentioned SID list 2.
  • the network device A adds the SID list 2 to the service message 1, which is used to guide the forwarding of the service message 1.
  • network device A also uses the destination address and the third identifier in the service message 2, and the segment list obtained from Table 1 is SID list 3, including SID B, SID C, SID E, and SID F, which are respectively network device B ,
  • SID list 3 including SID B, SID C, SID E, and SID F, which are respectively network device B .
  • the segment identifiers of network equipment C, network equipment E, and network equipment F, that is, the forwarding path corresponding to SID list 3 passes through network equipment B, network equipment C, and network equipment E to reach network equipment F. This is a way to meet high-bandwidth network performance The required forwarding path.
  • the network device A adds the SID list 3 to the service message 2 to guide the forwarding of the service message 2. It can be seen that service message 1 and service message 2 propose different network performance requirements, and network device A can provide different forwarding paths for different network performance requirements in different service messages, so that in the entire network, the network The presentation of performance requirements is more flexible.
  • Table 1 is only an example of the mapping relationship between the combination of the final destination address and network performance requirements and the segment list. There can be many mapping relationships between the combination of the final destination address and network performance requirements and the segment list.
  • the final destination address can also be expressed as the segment identifier of the receiving device X or other identification information of the receiving device X
  • the network performance requirement information can also be expressed as a color attribute, such as green, and so on.
  • S213 The network device 202 forwards the service packet through the forwarding path corresponding to the segment list.
  • the network device 202 forwards the service packet through the forwarding path corresponding to the segment list means that the network device 202 sends the service packet to the first network device on the forwarding path, and the network device and each network device on the forwarding path follow the segment list Instructs to send the service packets to the next network device on the forwarding path in sequence.
  • network device A sends service message 1 through the forwarding path corresponding to SID list 2, that is, service message 1 is sent from network device A to network device B, and then from network device E to Network equipment F.
  • the network device F can continue to send the service message 1 to the receiving device X according to the final destination address of the service message 1 as the receiving device X.
  • the foregoing forwarding path composed of network device A, network device B, network device C, network device E, and network device F is a low-latency forwarding path, which matches the network performance requirements of service message 1 proposed by the host, thereby supporting
  • the host directly proposes network performance requirements, which makes the way to propose network performance requirements more flexible.
  • FIG. 6 shows a schematic diagram of a possible structure of the network device involved in the foregoing embodiment.
  • the network device 600 can implement the functions of the network device 202 in the embodiment shown in FIG. 2.
  • the network device 600 includes: a receiving unit 601, a processing unit 602, and a sending unit 603. These units can perform the corresponding functions of the network device in the above method. for example,
  • the receiving unit 601 is configured to receive a first service message from a host, where the first service message includes a first identifier, and the first identifier indicates a network performance requirement of the first service message;
  • the processing unit 602 is configured to add a segment list to the first service message according to an element to obtain a second service message, wherein the element includes the first identifier, and the forwarding path corresponding to the segment list satisfies The network performance requirements;
  • the sending unit 603 is configured to forward the second service packet through the forwarding path.
  • FIG. 7 shows another possible structural schematic diagram of the network device 202 involved in the foregoing embodiment.
  • the network device 700 includes a processor 702, a network interface 703, and a memory 701. among them,
  • the memory 701 is used to store instructions; in the case of implementing the embodiment shown in FIG. 6 and each unit described in the embodiment of FIG. 6 is realized by software, it is required to perform the functions of the processing unit 602 in FIG. 6
  • the software or program code of the software is stored in the memory 701.
  • the processor 702 is configured to execute instructions in the memory 701, and execute the foregoing method for sending messages in the embodiment shown in FIG. 2; the processor 702 may be a central processing unit (CPU) or a general-purpose processor, Digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware Parts or any combination thereof. It can implement or execute various logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present invention.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the network interface 703 is used to communicate with other network devices.
  • the network interface 703 may be an Ethernet (Ethernet) interface or an asynchronous transfer mode (Asynchronous Transfer Mode, ATM) interface, etc.
  • the network interface 703, the processor 702, and the memory 701 are connected to each other.
  • the network interface 703, the processor 702, and the memory 701 are connected to each other via a bus; the bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus Wait.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the processor 702 is configured to receive a first service packet from the host through the network interface 703, the first service packet includes a first identifier, and the first identifier indicates the first service packet Network performance requirements; add a segment list to the first service message according to an element to obtain a second service message, wherein the element includes the first identifier, and the forwarding path corresponding to the segment list satisfies all The network performance requirements; the second service packet is forwarded through the forwarding path through the network interface 703.
  • the processor 702 please refer to the detailed description of the processes S212 and S213 in the embodiment shown in FIG. 2, which will not be repeated here.
  • the network interface 703 is used for the network device 700 to receive and send messages through the network system.
  • FIG. 8 shows a schematic diagram of a possible structure of the host involved in the foregoing embodiment.
  • the host 800 can implement the function of the host 201 in the embodiment shown in FIG. 2.
  • the network device 800 includes: a sending unit 801. This unit can perform the corresponding functions of the host in the above method. for example,
  • the sending unit 801 is configured to send a first service message to a network device, where the first service message includes a first identifier, and the first identifier indicates a network performance requirement of the first service message.
  • the host 800 further includes: a receiving unit 802. This unit can perform the corresponding functions of the host in the above method. for example,
  • the receiving unit 802 is configured to receive a control message from the network device, where the control message includes the second identifier; wherein, the first service message includes a first segment identifier, and the first segment identifier It includes a location field and a function field, the location field includes the address of the network device, and the function field includes a second identifier and the first identifier.
  • the host 800 further includes a processing unit 803. This unit can perform the corresponding functions of the host in the above method example. for example,
  • the processing unit 803 is configured to run a first application program and a second application program, the first application program is different from the second application program, and the first service message is a service message of the first application program , The second service message is a service message of the second application;
  • the sending unit 801 is further configured to send the second service message to the network device, where the second service message includes a third identifier, and the third identifier indicates the network performance requirement of the second service message , The third identifier is different from the first identifier.
  • FIG. 9 shows a schematic diagram of a possible structure of the host involved in the foregoing embodiment.
  • the host 900 includes a processor 902, a network interface 903, and a memory 901. among them,
  • the memory 901 is used to store instructions; in the case of implementing the embodiment shown in FIG. 8 and the units described in the embodiment in FIG. 8 are realized by software, it is required to execute the function of the 8 sending unit 801 in FIG. 8
  • the software or program code of the software is stored in the memory 901.
  • the processor 902 is configured to execute instructions in the memory 901, and execute the foregoing method for sending messages in the embodiment shown in FIG. 2; the processor 902 may be a CPU, a general-purpose processor, DSP, ASIC, FPGA or other programmable Logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present invention.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the network interface 903 is used to communicate with other network devices.
  • the network interface 903 may be a wired interface or a wireless interface.
  • the network interface 903, the processor 902, and the memory 901 are connected to each other.
  • the network interface 903, the processor 902, and the memory 901 are connected to each other through a bus; the bus may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the processor 902 is configured to send a first service message to the network device through the network interface 903, where the first service message includes a first identifier, and the first identifier represents the first service message Network performance requirements.
  • the processor 902 please refer to the detailed description of the process S211 in the embodiment shown in FIG. 2, which will not be repeated here.
  • the network interface 903 is used by the host 900 to send and receive messages through the network system.
  • the specific process please refer to the detailed description of S211 in the embodiment shown in FIG. 2, which will not be repeated here.
  • FIG. 10 shows a schematic diagram of a possible structure of a network system provided by an embodiment of the present invention.
  • the network system 1000 includes a host 1001 and a network device 1002.
  • the host 1001 in the network system can execute the processing steps of the host 201 in the embodiment shown in FIG. 2, and the network device 1002 in the network system can execute the processing steps of the network device 202 in the embodiment shown in FIG. 2.
  • the host 1001 in the network system may be the host 800 in the embodiment shown in FIG. 8, and the network device 1002 may be the network device 600 in the embodiment shown in FIG. 6, or correspondingly, in the network system
  • the host 1001 may be the host 900 in the embodiment shown in FIG. 9, and the network device 1002 may be the network device 700 in the embodiment shown in FIG. 7.
  • the host is configured to send a first service message to a network device, the first service message includes a first identifier, and the first identifier indicates a network performance requirement of the first service message.
  • the network device is configured to receive a first service message from the host, add a segment list to the first service message according to elements, to obtain a second service message, and forward it through the corresponding segment list
  • the path forwards the second service message, wherein the element includes the first identifier, and the forwarding path meets the network performance requirement.
  • the embodiment of the present invention also provides a non-transitory storage medium for storing the software instructions used in the foregoing embodiment, which includes a program for executing the method shown in the foregoing embodiment, when it is on a computer or network device When executed, the computer or network device shown is caused to execute the method in the foregoing method embodiment.
  • the embodiment of the present invention also provides a computer program product including computer program instructions, which when the computer program product runs on a computer, causes a network node to execute the method in the foregoing method embodiment.
  • the "first” of the first service message, the first identifier, the first segment identifier, and the first application program mentioned in the embodiment of the present invention is only used as a name identifier, and does not represent the first in order. This rule also applies to "second”, “third” and “fourth”.
  • any of the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physically separate.
  • the physical unit can be located in one place or distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines. Those of ordinary skill in the art can understand and implement it without creative work.
  • the steps of the method or algorithm described in the disclosure of the embodiment of the present invention may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory (EPROM, EEPROM), hard disk, mobile hard disk, optical disk, or any other form of storage medium known in the art.
  • the storage medium is coupled to the processor, so that the processor can read information from the storage medium.
  • the storage medium may also be an integral part of the processor.

Abstract

公开一种支持主机提出网络性能需求的报文发送方法。该方法包括：网络设备接收来自主机的第一业务报文，第一业务报文包括第一标识，第一标识表示第一业务报文的网络性能需求；网络设备根据要素向第一业务报文中添加段列表，以获得第二业务报文，其中，要素包括第一标识，段列表对应的转发路径满足网络性能需求；网络设备通过转发路径转发第二业务报文。网关设备直接接收主机提出的网络性能需求，使得网络性能需求的获取方式更加灵活，并且网关设备将主机提出的网络性能需求作为确定业务报文转发路径的要素，提升网络效率。

Description

主机网络性能需求可编程化的方法、设备和系统
本申请要求于2019年9月6日提交的申请号为201910844539.8、发明名称为“主机网络性能需求可编程化的方法、设备和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种段路由(segment routing,SR)网络中主机网络性能需求可编程化的方法、设备和系统。
背景技术
SR是一种基于源路由理念设计的、在网络上转发数据包的协议，支持在源网络设备显式指定数据包转发路径。
发明内容
本申请提供了一种发送报文的方法、设备和系统，支持发送报文的主机直接向SR网络提出可编程的网络性能需求，用于解决配置的网络性能需求不够灵活的技术问题。
第一方面，本申请提供了一种发送报文的方法。网络设备接收来自主机的第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求；所述网络设备根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，其中，所述要素包括所述第一标识，所述段列表对应的转发路径满足所述网络性能需求；所述网络设备通过所述转发路径转发所述第二业务报文。
该方法可以由SR网络的网关设备执行。网关设备直接接收主机提出的网络性能需求，使得网络性能需求的获取方式更加灵活，并且网关设备将主机提出的网络性能需求作为确定业务报文转发路径的要素，提升网络效率。
在一种可能的设计中，在所述网络设备接收来自所述主机的所述第一业务报文之前，所述方法还包括：所述网络设备向所述主机发送控制报文，所述控制报文包括第二标识；其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括所述第一标识和所述第二标识。网络设备从来自主机的控制报文中获得接收网络性能需求的功能所对应的类型数值，将代表网络性能需求的第一标识以该功能的参数的形式携带在业务报文中。
在一种可能的设计中，所述要素还包括所述第一业务报文的目的地址。
在一种可能的设计中，所述第一标识的值表示基于服务级别协议要求的颜色。
第二方面，本申请提供了一种提出网络性能需求的方法。主机向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文 的网络性能需求。
该方法可以由主机执行，向业务报文中添加网络性能需求后发送至网关设备，主机直接提出网络性能需求的方式更加灵活。
在一种可能的设计中，在所述主机向所述网络设备发送所述第一业务报文之前，所述方法还包括：所述主机接收来自所述网络设备的控制报文，所述控制报文包括第二标识；其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括所述第一标识和所述第二标识。
在一种可能的设计中，所述主机运行第一应用程序和第二应用程序，所述第一应用程序与所述第二应用程序不同，所述第一业务报文是所述第一应用程序的业务报文，第二业务报文是所述第二应用程序的业务报文，所述方法还包括：所述主机向所述网络设备发送所述第二业务报文，所述第二业务报文包括第三标识，所述第三标识表示所述第二业务报文的网络性能需求，所述第三标识与所述第一标识不同。
第三方面，本申请提供了一种网络设备，执行第一方面或第一方面的任意一种可能的实现方式中的方法。具体地，该网络设备包括用于执行第一方面或第一方面的任意一种可能的实现方式中的方法的单元。
第四方面，本申请提供了一种主机，执行第二方面或第二方面的任意一种可能的实现方式中的方法。具体地，该主机包括用于执行第二方面或第二方面的任意一种可能的实现方式中的方法的单元。
第五方面，本申请提供了一种网络设备，该网络设备包括：处理器、网络接口和存储器。网络接口可以是收发器。存储器可以用于存储程序代码，处理器用于调用存储器中的程序代码执行前述第一方面或第一方面的任意一种可能的实现方式，此处不再赘述。
第六方面，本申请提供了一种主机，该主机包括：处理器、网络接口和存储器。网络接口可以是收发器。存储器可以用于存储程序代码，处理器用于调用存储器中的程序代码执行前述第二方面或第二方面的任意一种可能的实现方式，此处不再赘述。
第七方面，本申请提供了一种网络系统，该网络系统包括前述第三方面提供的网络设备和第四方面提供的主机，或者该网络系统包括前述第五方面提供的网络设备和第六方面提供的主机。
第八方面，本申请提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第九方面，本申请提供了一种包括计算机程序指令的计算机程序产品，当该计算机程序产品在网络设备上运行时，使得网络设备执行第一方面、第二方面第一方面的任意一种可能的实现方式或第二方面的任意一种可能的实现方式中提供的方法。
第十方面，本申请提供了一种芯片，包括存储器和处理器，存储器用于存储计算机程序，处理器用于从存储器中调用并运行该计算机程序，以执行上述第一方面 及其第一方面任意可能的实现方式中的方法，或者，处理器执行第二方面或第二方面任意可能的实现方式中的方法。
可选地，上述芯片仅包括处理器，处理器用于读取并执行存储器中存储的计算机程序，当计算机程序被执行时，处理器执行第一方面或第一方面任意可能的实现方式中的方法，或者，处理器执行第二方面或第二方面任意可能的实现方式中的方法。
附图说明
图1为本发明实施例提供的一种网络场景示意图。
图2为本发明实施例提供的一种发送报文的方法。
图3为本发明实施例提供的一种RA报文的格式。
图4为本发明实施例提供的一种段标识的结构。
图5为本发明实施例提供的一种报文头格式。
图6为本发明实施例提供的一种网络设备的结构示意图。
图7为本发明实施例提供的一种网络设备的结构示意图。
图8为本发明实施例提供的一种网络设备的结构示意图。
图9为本发明实施例提供的一种网络设备的结构示意图。
图10为本发明实施例提供的一种网络系统的结构示意图。
具体实施方式
下面结合附图，对本发明的实施例进行描述。
图1示出了本发明实施例的一种可能的应用场景。该场景包括SR网络，该网络包括若干网络设备，例如网络设备A、网络设备B、网络设备C、网络设备D、网络设备E和网络设备F。这些网络设备可以是路由器、交换机、或者软件定义网络(software-defined networking，SDN)结构中的转发器。其中，网络设备A为主机的网关。在本发明的实施例中，网关用于在两个网络间传递数据包，例如，可以将两个使用不同协议的网络连接在一起，并对两个网络段中的使用不同传输协议的数据进行翻译转换。主机通过网络设备A连接SR网络。网络设备A引导来自主机的流量通过具体的转发路径进行转发。主机可以是终端设备，例如：个人计算机、手机或平板电脑等。主机也可以是服务提供计算机，例如：服务器等。
本发明实施例提供了发送报文的方法及基于该方法的设备和系统。该方法、设备和系统基于同一发明构思。方法、设备和系统解决问题的原理相似，因此，方法、设备和系统的实施例可以相互参见，相同或类似之处不再赘述。
参阅图2，本发明实施例提供了一种发送报文的方法。在该方法中，SR网络的网关设备直接接收主机提出的网络性能需求，使得网络性能需求的获取方式更加灵活。在图2所示的实施例中，主机201可以是图1中的主机，网络设备202可以是SR网络的网关，例如图1中的网络设备A。该方法包括：
S211，主机201向网络设备202发送业务报文，业务报文包括第一标识，所述第一标识 表示所述业务报文的网络性能需求。
所述业务报文可以是主机201生成的业务报文。具体可以是主机201运行的应用程序生成业务报文。主机201可以是个人计算机、手机或平板电脑等终端设备，主机201可以运行不同的应用程序。这些应用程序可以分别生成不同的业务报文。例如，主机201运行应用程序1和应用程序2，应用程序1和应用程序2是不同的应用程序。应用程序1生成业务报文1，即业务报文1是应用程序1的业务报文，应用程序2生成业务报文2，即业务报文2是应用程序2的业务报文。
所述业务报文中可以携带表示该业务报文的网络性能需求的标识。所述业务报文的网络性能需求可以是服务等级协议(Service Level Agreement,SLA)要求，例如低时延、大带宽、短路径跳数等等。业务报文中携带的标识的值可以表示SLA需求。例如，可以在每项SLA要求与每个标识值之间建立映射关系，从而每个标识值可以用来表示一项SLA需求。例如，也可以将SLA需求的颜色属性值作为业务报文中携带的标识值。每个SLA要求可以表示为一种颜色属性，每种颜色属性映射为一个特定数值，该颜色属性与特定数值的对应关系是全网统一的。例如，低时延的网络性能需求可以表示为绿色，对应数值为20。例如，大带宽的网络性能需求可以表示为蓝色，对应数值为40。业务报文中携带的标识的值可以是上述颜色属性映射的特定数值，例如20。可选地，网络性能需求还可以是网络性能参数值，业务报文中携带的标识的值为该参数值。例如，网络性能需求是端到端时延上限为10ms，则业务报文中携带的标识的值可以是10；网络性能需求是带宽为100M，则业务报文中携带的标识的值可以是100。可选地，业务报文中携带的标识的值为满足网络性能需求的报文转发路径的标识。例如，满足网络性能需求的报文转发路径为第一路径，该第一路径在网络中的标识为path A，则业务报文中携带的标识的值可以是A。可选地，所述业务报文中可以同时包括多项网络性能需求。
并且，不同的业务报文可以携带不同的标识，不同应用程序的业务报文也可以携带不同的标识。例如，应用程序1生成的业务报文1包括第一标识，第一标识的值为20，表示绿色的颜色属性，即业务报文1的网络性能需求为低时延，应用程序2生成的业务报文2包括第二标识，第二标识的值为40，表示蓝色的颜色属性，即业务报文2的网络性能需求为大带宽。因而，通过在业务报文中携带表示网络性能需求的标识，主机201能够直接提出自身的网络性能需求，更加灵活。并且，针对不同的业务报文能够提出不同的网络性能需求，或者基于不同的应用程序能够提出不同的网络性能需求。
在一个例子中，在主机201获得包括所述第一标识的业务报文之前，网络设备202向主机201发送控制报文，用于向主机201通告其可以提出自身的网络性能需求。所述控制报文可以是邻居发现协议(Neighbor Discovery Protocol，NDP)中的路由器通告(router advertisement,RA)报文。RA报文由网关周期性地向主机发送，或者响应于主机的路由器请求(router solicitation)报文而发送，用于向主机通告网关的相关信息。结合图1所示的应用场景，主机201为图1所示的主机，网络设备202为该主机的网关，即网络设备A。网络设备A向主机发送RA报文，用于通告网关的相关信息。图3示出了RA报文的格式，RA报文包括：类型(Type)字段、编码(Code)字段、校验和(Checksum)字段、跳数限制(Cur Hop Limit)字段、M标志位、O标志位、保留(Reserved)字段、路由生命周期(Router Lifetime)字段、可达时间(Reachable Time)字段、转发计时器(Retrans Timer)字段以 及选项(Options)字段。网络设备A可以对RA报文进行扩展。可选地，网络设备A可以在选项字段设置使能标志，该使能标志可以是特定数值的类型字段。例如，网络设备A可以在选项字段添加类型数值为38的选项作为使能标志。当主机接收到RA报文后，在选项字段中读取到类型数值为38的选项，即得知可以在向网络设备A发送的业务报文中携带第一标识，从而提出自身的网络性能需求。
当所述SR网络可以是SRv6网络时，网络设备202还可以通过所述控制报文向主机201通告接收网络性能需求的SRv6网络功能，在主机201生成的业务报文中，网络性能需求作为所述功能的参数被携带，进而，当该业务报文由主机201发送至网络设备202时，网络设备202能够通过所述功能接收并处理业务报文中的网络性能需求。SRv6网络具有多种功能，每种功能包括相应的操作步骤，用于实现特定的功能，在功能的操作步骤中可能涉及到相关的参数。每种功能可以用包括在SID中的特定数值的功能字段表示。每种参数也可以用包括在SID中的特定数值的参数字段表示，并且表示参数的参数字段通常放置在表示功能的功能字段之后。可选地，每种功能涉及的参数可以为多个，相应地，表示功能的类型字段之后可以跟随多个表示不同参数的不同参数字段。参见图4，SRv6网络中的SID可以包括两部分：位置(Locator)字段和功能(Function)字段。其中，位置字段包括网络设备地址前缀，用于定位到具体网络设备。功能字段包括该网络设备实现的SRv6网络的功能(Function)以及该功能涉及的参数(Argument)，其中，参数是可选的，当这个功能不涉及参数时，该参数字段中不包括参数。通常来说，SID的总长度为128比特。其中位置字段和功能字段分别为特定长度，且这些特定长度是可以通过网络设置进行改变的。例如，位置字段为64比特，功能字段为64比特。或者，位置字段为48比特，功能字段为80比特。在处理SID的过程中，网络设备查询本地段标识表(local SID table)，本地段标识表包括功能与特定数值的功能字段之间的映射关系，网络设备在本地段标识表中根据特定数值的功能字段确定该特定数值的功能字段所表示的功能。当SID的功能字段仅包括功能时，或者当SID的功能字段包括功能以及该功能涉及的参数时，在本地段标识表中都可以根据SID的功能字段确定出相应的功能。例如，在本地段标识表中代表接收网络性能需求的功能的功能字段表项为B112:0000:0000:0000，携带参数的功能字段即B112:0020:0000:0000。网络设备确定出功能字段所代表的功能为接收网络性能需求，并且根据该功能携带参数的格式识别其中的0020为参数，代表低时延的网络性能需求。可选地，SID的功能字段可以携带多项参数。例如，携带参数的功能字段可以是B112:0020:0010:0100，网络设备确定出功能字段所代表的功能为接收网络性能需求，并且根据该功能携带参数的格式识别其中的0020,0010和0100为参数，分别代表低时延、端到端时延上限为10ms和带宽需求100M。可选的，接收网络性能需求的功能可以是End.B6.Insert功能的变体(variation)，或者，接收网络性能需求的功能可以是End.B6.Encaps功能的变体。
例如，网络设备202向主机201发送的所述控制报文中可以包括第二标识，所述第二标识的值可以是接收网络性能需求的功能所对应的特定数值的功能字段。可选地，所述控制报文中还包括说明字段，用于对所述接收网络性能需求的功能与特定数值的功能字段之间的对应关系进行说明。例如，该说明字段可以是RA报文中的特定字段。例如，该说明字段可以是RA报文中的SRV6节点功能(Endpoint Function)字段。主机201生成包括所述第一标识和所述第二标识的业务报文。可选地，所述第二标识和所述第一标识可以包括在所 述业务报文的同一个SID中，所述第二标识和所述第一标识可以包括在该SID的功能字段中，所述第二标识的值用于表示接收网络性能需求的功能，所述第一标识的值用于表示网络性能需求，所述第一标识的值作为所述功能的参数。可选地，所述业务报文中SID的位置字段可以包括网络设备202的地址前缀，即所述业务报文中SID是网络设备202的段标识。在本发明实施例中，SID是网络设备202的段标识，是指SID的位置字段包括网络设备202的地址前缀，例如，SID可以是网络设备202的节点类段标识(node SID)，也可以是网络设备202的链路的邻接类段标识(adjacent SID)。以上关于段标识的解释也适用于除了网络设备202以外的其他网络设备。可选地，所述第二标识可以包括在所述控制报文的SID中。可选地，所述第二标识可以包括在该SID的功能字段中。可选地，所述控制报文中SID的位置字段可以包括网络设备202的地址前缀，即所述控制报文中SID是网络设备202的段标识。
结合图1所示的应用场景进行举例说明，网络设备A向主机发送RA报文，RA报文的选项字段包括类型数值为38的使能标志。RA报文中还包括网络设备A的段标识SID A1。例如，SID A1为1111:0000:0000:0000:B112:0000:0000:0000/h，长度为128比特，“/h”表示该数值被以十六进制表示。其中前64比特为位置字段，即1111:0000:0000:0000，匹配网络设备A的地址前缀。后64比特为功能字段，即B112:0000:0000:0000，包括第二标识B112::其中“::”表示全0，第二标识的值代表接收网络性能需求的功能。主机接收到网络设备A发送的RA报文，在RA报文中读取到类型数值为38的使能标志，获知可以向网络设备A直接提出网络性能需求，即在向网络设备A发送的业务报文中携带表示网络性能需求的第一标识。主机在RA报文中读取到所述第二标识B112::，并且在RA报文的SRV6Endpoint Function字段获取到对第二标识的值与接收网络性能需求的功能的对应关系，确定第二标识所表示的功能为接收网络性能需求。主机生成包括所述第一标识和所述第二标识的业务报文1。具体的，业务报文1可以包括网络设备A的段标识SID A2，SID A2为1111:0000:0000:0000:B112:0020:0000:0000。其中功能字段为B112:0020:0000:0000，包括第二标识B112以及第一标识0020，其中第一标识的值为20/h，表示业务报文1的网络性能需求为低时延。从而，主机通过在业务报文1中设置第一标识以直接表达自身的网络性能需求。
进而，包含第一标识和第二标识的网络设备202的段标识可以包括在所述业务报文的段路由头(segment routing header,SRH)中的段列表中。图5示出了IPv6报文头和SRH的格式，SRH在IPv6报文头之后。IPv6报文头包括：版本(Version)字段、流量分类(Traffic Class)字段、流标识(Flow Label)字段、有效载荷长度(Payload Length)字段、下一个头(Next Header)字段、跳限制(Hop Limit)字段、源地址(Source Address)字段、目的地址(Destination Address,DA)字段。SRH包括：、下一个头(Next Header)字段、头扩展长度(Hdr Ext Len)字段、路由类型(Routing Type)字段、段剩余(Segments Left)字段、最末条目(Last Entry)字段、标记(Flags)字段、标签(Tag)字段、段列表(Segment List)字段、可选的类型长度值对象(Optional TLV objects)字段。主机201生成业务报文后，在业务报文的SRH中封装段列表，将封装好的业务报文发送出去。所述段列表包括第一段标识和第二段标识，所述第一段标识可以是网络设备202的段标识。结合以上描述，网络设备202的段标识包括位置字段和功能字段，所述位置字段包括所述网络设备202的地址前缀，所述功能字段包括所述第二标识和所述第一标识。所述第二段标识包括所述业务报文的目的地址，该目的 地址是业务报文的接收设备的地址前缀。
结合图1所示的应用场景进行举例说明，主机向网络设备A发送业务报文1，业务报文1的目的地址为接收设备X，业务报文1包括段列表1，即SID list 1。该SID list 1包括两个段标识SID X和为SID A2。SIDA2为网络设备A的段标识，SID A2可以为1111:0000:0000:0000:B112:0020:0000:0000，其中位置字段包括网络设备A的地址前缀，功能字段包括第二标识和第一标识。SID X可以为1234:5678:0000:0000:0000:0000:0000:0000，长度为128比特，其中前64比特为位置字段，包括接收设备X的地址前缀，即1234:5678:0000:0000/64，也是业务报文1的目的地址。可选地，SID X也可以是传统的IPv6地址，例如2001:0db8:85e3:0000:0000:8a2e:0370:7334。
S212，网络设备202接收来自主机201的所述业务报文，根据业务报文中的第一标识向业务报文中添加段列表，所述段列表对应的转发路径满足所述业务报文的网络性能需求。网络设备202作为主机201的网关设备，接收来自主机201的业务报文，向业务报文中添加段列表后，进而通过段列表对应的转发路径将业务报文转发出去。在此过程中，网络设备202根据第一标识向业务报文中添加段列表，所添加的段列表对应的转发路径也满足业务报文的网络性能需求。从而确保业务报文通过满足其网络性能需求的转发路径进行转发，网络服务具有更强的针对性。可选地，网络设备202向所述业务报文中添加段列表时，所考虑的要素除了所述业务报文中的所述第一标识，还包括所述业务报文的目的地址，即网络设备202根据业务报文的目的地址和第一标识向业务报文中添加段列表。所述业务报文的目的地址是所述业务报文的接收设备的地址前缀。
结合图1所示的应用场景进行举例说明，网络设备A接收主机发送的业务报文1，业务报文1的目的地址为接收设备X，业务报文1包括第一标识，第一标识的值为20，表示低时延的网络性能需求。网络设备A根据目的地址和第一标识确定为业务报文1添加的段列表。例如，网络设备A可以获得目的地址和网络性能需求的组合与段列表的映射关系，如表1所示。网络设备A根据目的地址和第一标识，通过表1获得的段列表为SID list 2，包括SID B,SID D,SID E,SID F，分别为网络设备B、网络设备D、网络设备E和网络设备F的段标识，即SID list 2对应的转发路径经过网络设备B、网络设备D、网络设备E，到达网络设备F，这是一条满足低时延网络性能需求的转发路径。网络设备A将SID list 2添加至业务报文1，用于指导业务报文1的转发。从而，网络提供的服务能够满足业务报文1直接提出的网络性能需求，网络性能需求的提出方式更加灵活。
表1
Figure PCTCN2020113363-appb-000001
结合以上描述，当对应于接收网络性能需求的功能的特定数值的功能字段携带在所述业务报文中时，网络设备202通过该功能接收主机201提出的网络性能需求，并根据该网络性能需求向业务报文中添加段列表，所述段列表对应的转发路径满足所述业务报文的网络 性能需求。
结合图1所示的应用场景进行举例说明，网络设备A接收主机发送的业务报文1，处理业务报文1的SRH中的段列表，该段列表可以是上述SID list 1，包括SID X和SID A2，其中SID X为接收设备X的段标识，具体为1234:5678:0000:0000:0000:0000:0000:0000，SID A2为网络设备A的段标识，具体为1111:0000:0000:0000:B112:0020:0000:0000。网络设备A从DA字段中获得SID A2，匹配到本地local sid tabel的1111:0000:0000:0000:B112:0000:0000:0000表项，确定其中的功能字段，即B112，执行该功能字段所代表的功能。网络设备A执行该功能字段所代表的功能的具体过程可以包括，读取功能字段后面的参数字段，获取参数字段中代表网络性能需求的数值，即数值20；根据更新后的SL在段列表中找到业务报文的最终目的地址，即接收设备X的段标识SID X，根据数值20和SID X，从上述表1中获得相应的段列表，即SID list 2；将SID list 2添加至业务报文1，用于指导业务报文1的转发。
结合以上描述，接收网络性能需求的功能可以是End.B6.Insert功能的变体，其具体执行过程包括将所述段列表为一个新的SRH头插入。或者，接收网络性能需求的功能可以是End.B6.Encaps功能的变体，其具体执行过程包括为报文封装新的IPv6报文头，并插入携带了所述段列表的SRH头。
在一个例子中，网络设备202可以接收不同的业务报文，不同的业务报文中包括不同的网络性能需求。网络设备202根据不同的网络性能需求，为不同的业务报文添加不同的段列表，从而使得不同的业务报文通过满足其网络性能需求的转发路径发送出去。
结合图1所示的应用场景进行举例说明，网络设备A接收主机发送的业务报文1和业务报文2，业务报文1和业务报文2的最终目的地址均为接收设备X。业务报文1包括第一标识，第一标识的值为20，表示低时延的网络性能需求。业务报文2包括第三标识，第三标识的值为40，表示大带宽的网络性能需求。例如，网络设备A可以获得不同的目的地址和网络性能需求的组合与不同的段列表的映射关系，如表1所示。网络设备A分别根据业务报文1和业务报文2中的目的地址和网络性能需求确定它们的转发路径。具体的，网络设备A根据业务报文1中的目的地址和第一标识，通过表1获得的段列表为SID list 2，与上述SID list 2的具体情况相同。网络设备A将SID list 2添加至业务报文1，用于指导业务报文1的转发。并且，网络设备A还根据业务报文2中的目的地址和第三标识，通过表1获得的段列表为SID list 3，包括SID B,SID C,SID E,SID F，分别为网络设备B、网络设备C、网络设备E和网络设备F的段标识，即SID list 3对应的转发路径经过网络设备B、网络设备C、网络设备E，到达网络设备F，这是一条满足大带宽网络性能需求的转发路径。网络设备A将SID list 3添加至业务报文2，用于指导业务报文2的转发。由此可见，业务报文1和业务报文2提出了不同的网络性能需求，网络设备A能够针对不同的业务报文中的不同网络性能需求提供不同的转发路径，从而在整个网络中，网络性能需求的提出方式更加灵活。
可以理解的是，表1只是给出了最终目的地址和网络性能需求的组合与段列表的映射关系的一种例子，最终目的地址和网络性能需求的组合与段列表的映射关系还可以有很多种形式，例如，其中最终目的地址还可以表示为接收设备X的段标识或者接收设备X的其他标识信息，网络性能需求信息还可以表示为颜色属性，如绿色，等等。
S213，网络设备202通过所述段列表对应的转发路径转发业务报文。
网络设备202通过段列表对应的转发路径转发业务报文是指，网络设备202将业务报文发送给转发路径上的第一个网络设备，该网络设备以及转发路径上的各个网络设备按照段列表的指示将业务报文依次发送给转发路径上的下一网络设备。结合图1所示的应用场景，网络设备A通过SID list 2对应的转发路径将业务报文1发送出去，即业务报文1由网络设备A发送至网络设备B，进而由网络设备E发送至网络设备F。网络设备F可以根据业务报文1的最终目的地址为接收设备X，继续将业务报文1向接收设备X发送。上述由网络设备A、网络设备B、网络设备C、网络设备E和网络设备F组成的转发路径为低时延的转发路径，与主机提出的业务报文1的网络性能需求相匹配，从而支持主机直接提出网络性能需求，使得网络性能需求的提出方式更加灵活。
图6示出了上述实施例中所涉及的网络设备的一种可能的结构示意图，网络设备600可以实现图2所示实施例中网络设备202的功能。参阅图6，该网络设备600包括：接收单元601、处理单元602和发送单元603。这些单元可以执行上述方法中网络设备的相应功能。举例来说，
接收单元601，用于接收来自主机的第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求；
处理单元602，用于根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，其中，所述要素包括所述第一标识，所述段列表对应的转发路径满足所述网络性能需求；
发送单元603，用于通过所述转发路径转发所述第二业务报文。
图7示出上述实施例中所涉及的网络设备202的另一种可能的结构示意图。网络设备700包括：处理器702、网络接口703以及存储器701。其中，
存储器701，用于存储指令；在实现图6所示实施例的情况下，且图6实施例中所描述的各单元为通过软件实现的情况下，执行图6中的处理单元602功能所需的软件或程序代码存储在存储器701中。
处理器702，用于执行存储器701中的指令，执行上述应用于图2所示实施例中发送报文的方法；处理器702可以是中央处理器(central processing unit，CPU)、通用处理器，数字信号处理器(digital signal processor，DSP)、专用集成电路(application-specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明实施例公开内容所描述的各种逻辑方框、模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。
网络接口703，用于与其他网络设备通信。网络接口703可以为以太网(Ethernet)接口或异步传输模式(Asynchronous Transfer Mode，ATM)接口等。
网络接口703、处理器702以及存储器701相互连接。例如，网络接口703、处理器702以及存储器701通过总线相互连接；总线可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在具体实施例中，处理器702用于通过网络接口703接收来自主机的第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求；根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，其中，所述要素包括所述第一标识，所述段列表对应的转发路径满足所述网络性能需求；通过网络接口703通过所述转发路径转发所述第二业务报文。该处理器702的详细处理过程请参考上述图2所示实施例中的过程S212，S213的详细描述，这里不再赘述。
网络接口703用于网络设备700通过网络系统接收和发送报文。具体的过程请参考上述图2所示实施例中S212，S213的详细描述，这里不再赘述。
图8示出了上述实施例中所涉及的主机的一种可能的结构示意图，该主机800可以实现图2所示实施例中主机201的功能。参阅图8，网络设备800包括：发送单元801。该单元可以执行上述方法中主机的相应功能。举例来说，
发送单元801，用于向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求。
在一个例子中，主机800还包括：接收单元802。该单元可以执行上述方法中主机的相应功能。举例来说，
接收单元802，用于接收来自所述网络设备的控制报文，所述控制报文包括所述第二标识；其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括第二标识和所述第一标识。
在一个例子中，主机800还包括：处理单元803。该单元可以执行上述方法例子中主机的相应功能。举例来说，
处理单元803，用于运行第一应用程序和第二应用程序，所述第一应用程序与所述第二应用程序不同，所述第一业务报文是所述第一应用程序的业务报文，第二业务报文是所述第二应用程序的业务报文；
发送单元801，还用于向所述网络设备发送所述第二业务报文，所述第二业务报文包括第三标识，所述第三标识表示所述第二业务报文的网络性能需求，所述第三标识与所述第一标识不同。
图9示出了上述实施例中所涉及的主机的一种可能的结构示意图，主机900包括：处理器902、网络接口903以及存储器901。其中，
存储器901，用于存储指令；在实现图8所示实施例的情况下，且图8实施例中所描述的各单元为通过软件实现的情况下，执行图8中8发送单元801功能所需的软件或程序代码存储在存储器901中。
处理器902，用于执行存储器901中的指令，执行上述应用于图2所示实施例中发送报文的方法；处理器902可以是CPU、通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明实施例公开内容所描述的各种逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。
网络接口903，用于与其他网络设备通信。网络接口903可以为有线接口或无线接口。
网络接口903、处理器902以及存储器901相互连接。例如，网络接口903、处理器902以及存储器901通过总线相互连接；总线可以是PCI总线或EISA总线等。所述总线可以分 为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在具体实施例中，处理器902用于通过网络接口903向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求。该处理器902的详细处理过程请参考上述图2所示实施例中的过程S211的详细描述，这里不再赘述。
网络接口903用于主机900通过网络系统收发报文。具体的过程请参考上述图2所示实施例中S211的详细描述，这里不再赘述。
参阅图10所示，图10示出本发明实施例提供的一种网络系统的可能的结构示意图。网络系统1000包括主机1001和网络设备1002。所述网络系统中的主机1001可以执行图2所示实施例中主机201的处理步骤，所述网络系统中的网络设备1002可以执行图2所示实施例中网络设备202的处理步骤。相应的，所述网络系统中的主机1001可以为图8所示实施例的主机800，所述网络设备1002可以为图6所示实施例的网络设备600，或者相应的，所述网络系统中的主机1001可以为图9所示实施例的主机900，所述网络设备1002可以为图7所示实施例的网络设备700。
具体的，所述主机，用于向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求。
所述网络设备，用于接收来自所述主机的第一业务报文，根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，通过所述段列表对应的转发路径转发所述第二业务报文，其中，所述要素包括所述第一标识，所述转发路径满足所述网络性能需求。
本发明实施例还提供了一种非瞬态存储介质，用于储存前述实施例中所用的软件指令，其包括用于执行前述实施例所示的方法的程序，当其在计算机或网络设备上执行时，使得所示计算机或网络设备执行前述方法实施例中的方法。
本发明实施例还提供了一种包括计算机程序指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得网络节点执行前述方法实施例中的方法。
本发明实施例中提到的第一业务报文、第一标识、第一段标识和第一应用程序的“第一”只是用来做名字标识，并不代表顺序上的第一。该规则同样适用于“第二”、“第三”和“第四”等。
需说明的是，以上描述的任意装置实施例都仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本发明提供的网络设备或主机的实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable ROM，EPROM)、电 可擦可编程只读存储器(electrically EPROM，EEPROM)、硬盘、移动硬盘、光盘或者本领域熟知的任何其它形式的存储介质中。存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息。当然，存储介质也可以是处理器的组成部分。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、替换、改进等，均应包括在本发明的保护范围之内。

Claims (16)

  1. 一种发送报文的方法，其特征在于，所述方法包括：
    网络设备接收来自主机的第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求；
    所述网络设备根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，其中，所述要素包括所述第一标识，所述段列表对应的转发路径满足所述网络性能需求；
    所述网络设备通过所述转发路径转发所述第二业务报文。
  2. 根据权利要求1所述的方法，其特征在于，在所述网络设备接收来自所述主机的所述第一业务报文之前，所述方法还包括：
    所述网络设备向所述主机发送控制报文，所述控制报文包括第二标识；
    其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括所述第一标识和所述第二标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述要素还包括所述第一业务报文的目的地址。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一标识的值表示基于服务级别协议要求的颜色。
  5. 一种提出网络性能需求的方法，其特征在于，所述方法包括：
    主机向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求。
  6. 根据权利要求5所述的方法，其特征在于，在所述主机向所述网络设备发送所述第一业务报文之前，所述方法还包括：
    所述主机接收来自所述网络设备的控制报文，所述控制报文包括第二标识；
    其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括所述第一标识和所述第二标识。
  7. 根据权利要求5或6所述的方法，其特征在于，所述第一业务报文包括段列表，所述段列表包括所述第一段标识和第二段标识，所述第二段标识包括所述第一业务报文的目的地址。
  8. 根据权利要求5-7任一项所述的方法，其特征在于，所述第一标识的值表示所述网络性能需求所对应的基于服务级别协议要求的颜色、所述网络性能需求的参数值 和/或所述转发路径的标识。
  9. 根据权利要求5-8任一项所述的方法，其特征在于，所述主机运行第一应用程序和第二应用程序，所述第一应用程序与所述第二应用程序不同，所述第一业务报文是所述第一应用程序的业务报文，第二业务报文是所述第二应用程序的业务报文，所述方法还包括：
    所述主机向所述网络设备发送所述第二业务报文，所述第二业务报文包括第三标识，所述第三标识表示所述第二业务报文的网络性能需求，所述第三标识与所述第一标识不同。
  10. 一种网络设备，其特征在于，所述网络设备包括：
    接收模块，用于接收来自主机的第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求；
    处理模块，用于根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，其中，所述要素包括所述第一标识，所述段列表对应的转发路径满足所述网络性能需求；
    发送模块，用于通过所述转发路径转发所述第二业务报文。
  11. 根据权利要求10所述的网络设备，其特征在于，
    所述发送模块，还用于向所述主机发送控制报文，所述控制报文包括第二标识；
    其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括所述第一标识和所述第二标识。
  12. 一种主机，其特征在于，所述主机包括：
    发送模块，用于向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求。
  13. 根据权利要求12所述的主机，其特征在于，所述主机还包括接收模块，
    所述接收模块，用于接收来自所述网络设备的控制报文，所述控制报文包括第二标识；
    其中，所述第一业务报文包括第一段标识，所述第一段标识包括位置字段和功能字段，所述位置字段包括所述网络设备的地址，所述功能字段包括所述第一标识和所述第二标识。
  14. 根据权利要求12或13所述的主机，其特征在于，所述主机还包括处理模块，
    所述处理模块，还用于运行第一应用程序和第二应用程序，所述第一应用程序与所述第二应用程序不同，所述第一业务报文是所述第一应用程序的业务报文，第二业务报文是所述第二应用程序的业务报文；
    所述发送模块，还用于向所述网络设备发送所述第二业务报文，所述第二业务报文包括第三标识，所述第三标识表示所述第二业务报文的网络性能需求，所述第三标识与所述第一标识不同。
  15. 一种网络系统，包括主机和网络设备，其特征在于，
    所述主机，用于向网络设备发送第一业务报文，所述第一业务报文包括第一标识，所述第一标识表示所述第一业务报文的网络性能需求；
    所述网络设备，用于接收来自所述主机的第一业务报文，根据要素向所述第一业务报文中添加段列表，以获得第二业务报文，通过所述段列表对应的转发路径转发所述第二业务报文，其中，所述要素包括所述第一标识，所述转发路径满足所述网络性能需求。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在计算机上运行时，使得所述计算机执行权利要求1-9任一项所述的方法。
PCT/CN2020/113363 2019-09-06 2020-09-04 主机网络性能需求可编程化的方法、设备和系统 WO2021043232A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20860842.2A EP4024782A4 (en) 2019-09-06 2020-09-04 METHOD BY WHICH HOST NETWORK PERFORMANCE REQUIREMENTS CAN BE PROGRAMMED, DEVICE AND SYSTEM
US17/686,983 US20220191138A1 (en) 2019-09-06 2022-03-04 Method for Making Host Network Performance Requirement Programmable, Device, and System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910844539.8A CN112468396B (zh) 2019-09-06 2019-09-06 主机网络性能需求可编程化的方法、设备和系统
CN201910844539.8 2019-09-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/686,983 Continuation US20220191138A1 (en) 2019-09-06 2022-03-04 Method for Making Host Network Performance Requirement Programmable, Device, and System

Publications (1)

Publication Number Publication Date
WO2021043232A1 true WO2021043232A1 (zh) 2021-03-11

Family

ID=74807029

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/113363 WO2021043232A1 (zh) 2019-09-06 2020-09-04 主机网络性能需求可编程化的方法、设备和系统

Country Status (4)

Country Link
US (1) US20220191138A1 (zh)
EP (1) EP4024782A4 (zh)
CN (1) CN112468396B (zh)
WO (1) WO2021043232A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4277226A1 (en) * 2022-05-12 2023-11-15 Huawei Technologies Co., Ltd. Packet transmission method, transmission control method, apparatus, and system

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113497754B (zh) * 2020-03-20 2023-02-10 华为技术有限公司 转发路径建立方法、装置以及计算机可读存储介质
CN115412976A (zh) * 2021-05-27 2022-11-29 华为技术有限公司 一种报文处理方法及相关设备
CN116489237A (zh) * 2022-01-13 2023-07-25 大唐移动通信设备有限公司 数据包处理方法、装置及网络设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871721A (zh) * 2015-01-19 2016-08-17 中兴通讯股份有限公司 一种段路由处理方法、处理装置及发送装置
WO2019005949A1 (en) * 2017-06-27 2019-01-03 Cisco Technology, Inc. GATEWAY OF SEGMENT ROUTING
CN109218201A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种生成转发表项的方法、控制器和网络设备
CN109561021A (zh) * 2017-09-25 2019-04-02 华为技术有限公司 一种报文转发的方法及网络设备
CN109981457A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 一种报文处理的方法、网络节点和系统
CN109981458A (zh) * 2019-03-08 2019-07-05 华为技术有限公司 一种确定报文转发路径的方法、网络节点及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106487537A (zh) * 2015-08-25 2017-03-08 中国电信股份有限公司 业务链实现方法以及策略控制平台
CN106549871B (zh) * 2015-09-22 2020-09-08 华为技术有限公司 一种报文处理的方法、设备和系统
CN106656781B (zh) * 2015-11-02 2020-12-11 中兴通讯股份有限公司 一种报文传输的方法、装置和系统
US10785148B2 (en) * 2016-02-15 2020-09-22 Telefonaktiebolaget Lm Ericsson (Publ) OSPF extensions for flexible path stitchng and selection for traffic transiting segment routing and MPLS networks
US20170310583A1 (en) * 2016-04-22 2017-10-26 Cisco Technology, Inc. Segment routing for load balancing
US10454821B2 (en) * 2016-10-14 2019-10-22 Cisco Technology, Inc. Creating and maintaining segment routed traffic engineering policies via border gateway protocol
US10454822B2 (en) * 2017-07-27 2019-10-22 Cisco Technology, Inc. Full-path validation in segment routing
CN109962847B (zh) * 2017-12-14 2021-07-30 中国电信股份有限公司 业务功能链报文的封装方法和装置及计算机可读存储介质
CN108512758B (zh) * 2018-03-07 2021-09-14 华为技术有限公司 报文处理方法、控制器以及转发设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871721A (zh) * 2015-01-19 2016-08-17 中兴通讯股份有限公司 一种段路由处理方法、处理装置及发送装置
WO2019005949A1 (en) * 2017-06-27 2019-01-03 Cisco Technology, Inc. GATEWAY OF SEGMENT ROUTING
CN109218201A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种生成转发表项的方法、控制器和网络设备
CN109561021A (zh) * 2017-09-25 2019-04-02 华为技术有限公司 一种报文转发的方法及网络设备
CN109981457A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 一种报文处理的方法、网络节点和系统
CN109981458A (zh) * 2019-03-08 2019-07-05 华为技术有限公司 一种确定报文转发路径的方法、网络节点及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
C. FILSFILS, ED.: "Segment Routing Architecture", INTERNET ENGINEERING TASK FORCE (IETF), 10 December 2015 (2015-12-10), pages 1 - 6, XP055788643, ISSN: 2070-1721, DOI: 10.1109/GLOCOM.2015.7417124 *
See also references of EP4024782A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4277226A1 (en) * 2022-05-12 2023-11-15 Huawei Technologies Co., Ltd. Packet transmission method, transmission control method, apparatus, and system

Also Published As

Publication number Publication date
EP4024782A1 (en) 2022-07-06
CN112468396B (zh) 2022-05-31
EP4024782A4 (en) 2022-08-31
CN112468396A (zh) 2021-03-09
US20220191138A1 (en) 2022-06-16

Similar Documents

Publication Publication Date Title
WO2021043232A1 (zh) 主机网络性能需求可编程化的方法、设备和系统
WO2020164473A1 (zh) 一种路径计算方法、装置及设备
WO2020182150A1 (zh) 报文处理方法、装置、设备及系统
US10412008B2 (en) Packet processing method, apparatus, and system
EP4231597A1 (en) Method for forwarding bier message, and device and system
WO2020156166A1 (zh) 用于处理报文的方法和装置
WO2021155759A1 (zh) 分段标识的处理方法及设备
WO2018032961A1 (zh) 一种管理信息的方法，装置及系统
WO2018032962A1 (zh) 一种信息同步的方法，装置及系统
CN111385209B (zh) 一种报文处理方法、报文转发方法、装置及设备
WO2021083341A1 (zh) 一种报文处理的方法、网络节点和系统
EP4099648A1 (en) Method for processing segment id, and apparatus
WO2021238746A1 (zh) 网络系统及其中的报文传输方法和相关装置
CN108075991B (zh) 报文转发方法及装置
EP4024807A1 (en) Message sending method and apparatus
CN113923161A (zh) 一种报文转发方法及装置
CN113141338B (zh) 一种消息生成方法、处理方法及装置
CN113630316A (zh) 一种数据传输方法及通信装置
WO2022228090A1 (zh) 路径学习方法、装置、业务节点及存储介质
JP7273125B2 (ja) ＢＩＥＲｖ６パケットを送信するための方法および第１のネットワークデバイス
US8583822B2 (en) Method and system for minimum frame size support for a communication protocol encapsulated over Ethernet
CN113285877A (zh) 一种报文转发的控制方法及相关装置
WO2023231438A1 (zh) 报文发送的方法、网络设备及系统
CN111447131A (zh) 报文解封装方法及装置、报文封装方法及装置
WO2023078144A1 (zh) 报文处理方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20860842

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020860842

Country of ref document: EP

Effective date: 20220331