Port resource reservation method, electronic device and storage medium

Abstract

The present invention relates to the field of communication technology, and discloses a port resource reservation method, electronic device and storage medium. The method of the present invention includes: receiving a request message for reserving resources for a service, and determining a resource reservation mode according to the request message; when it is determined that the resource reservation mode is an extended mode, obtaining the output port queue corresponding to the extended priority carried in the request message according to a preset first mapping relationship, and reserving resources for the service on the output port queue corresponding to the extended priority; wherein the first mapping relationship refers to the correspondence between the extended priority and the output port queue; obtaining a service identifier from the request message, and establishing a second mapping relationship; wherein the second mapping relationship refers to the mapping relationship between the service identifier and the extended priority. Through the above means, the number of service priorities in port resource reservation is expanded, providing fine-grained resource allocation services for the service, and further improving the utilization efficiency of port resources in the bridge device.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method, electronic equipment and storage medium for reserving port resources. Background Art

[0002] Currently, in the field of communications technology, Internet users are increasingly demanding multimedia applications on Ethernet networks, leading to the emergence of a variety of protocols for quality-of-service integration on the Internet. Among them, the IEEE 802.1Qat standard, proposed by the IEEE, provides a network stream reservation protocol (SRP). The SRP protocol is a distributed resource reservation protocol used to establish forwarding tables and reserve bandwidth resources for time-sensitive network (TSN) traffic. The Talker Advertisement message in the SRP protocol carries a 3-bit data structure priority field (Data Frame Priority). During the protocol operation, the corresponding reserved resource egress queue is found through the priority-to-traffic class mapping relationship proposed in IEEE 802.1Qav.

[0003] However, the inventors of this application found that in the prior art, the following situation often occurs: the SRP protocol reserves resources for the egress port queue based on the priority field, and the existing priority field with a length of 3 bits only supports a maximum of 7 categories, that is, it supports resource reservation on a maximum of 7 egress port queues, while the actual TSN service categories are far greater than 7 categories. When the number of egress port queues supported by the bridge device is greater than 8, the current SRP protocol cannot fully utilize the egress port queue resources supported by the bridge device to meet the actual needs of the TSN service. Summary of the Invention

[0004] The purpose of the embodiments of the present invention is to provide a port resource reservation method, an electronic device, and a storage medium, which can provide fine-grained resource allocation services for services.

[0005] To solve the above technical problems, an embodiment of the present invention provides a port resource reservation method, including: receiving a request message for reserving resources for a service, and determining a resource reservation method based on the request message; when it is determined that the resource reservation method is an extended method, obtaining the output port queue corresponding to the extended priority carried in the request message according to a preset first mapping relationship, and reserving resources for the service on the output port queue corresponding to the extended priority; wherein, the first mapping relationship refers to the correspondence between the extended priority and the output port queue; obtaining a service identifier from the request message, and establishing a second mapping relationship; wherein, the second mapping relationship refers to the mapping relationship between the service identifier and the extended priority.

[0006] An embodiment of the present invention also provides an electronic device, comprising: at least one processor; and at least one memory; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the port resource reservation method as described above.

[0007] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the port resource reservation method described above when executed by a processor.

[0008] Compared to the prior art, the embodiment of the present invention, when receiving a request message for reserving resources for a service, if it is determined from the request message that an extended method is currently used for resource reservation, then the output port queue corresponding to the extended priority carried in the request message is found based on a preset mapping relationship; then the service identifier of the service is obtained from the request message, and a mapping relationship between the service identifier and the extended priority is established. That is, in this embodiment, an extended method is proposed for resource reservation, a first mapping relationship between the extended priority and the output port queue is preset, and a second mapping relationship between the service identifier and the extended priority is established for the service based on the service identifier and the extended priority in the request message; through the first mapping relationship and the second mapping relationship, a mapping relationship between the service identifier, the extended priority, and the output port queue is determined for the service; through this extended method, the number of priorities that can be supported in resource allocation can be expanded based on the existing message transmission protocol, thereby making full use of the output port queue resources in the network device to provide fine-grained port resource reservation services for service messages.

[0009] In addition, after obtaining the service identifier from the request message and establishing the second mapping relationship, it also includes: receiving a service message and searching for the service identifier carried in the service message in the second mapping relationship; when the service identifier carried in the service message is found in the second mapping relationship, obtaining the first target queue according to the second mapping relationship and the first mapping relationship; the first target queue refers to the outbound port queue corresponding to the service identifier carried in the service message; placing the service message in the first target queue, and sending the service message based on the resources reserved at the target queue. This embodiment provides a method for finding the corresponding outbound port queue for the received service message after reserving resources in the outbound port queue based on an extended method; that is, the service identifier is preset in the service message, so that the outbound port queue of the service message can be determined according to the first mapping relationship and the second mapping relationship. Since there are more priority levels, more outbound port queues can be corresponding, thereby improving the utilization efficiency of port resources.

[0010] In addition, according to the port resource reservation method, after determining the method for reserving resources according to the request message, it also includes: when it is determined that the resource reservation method is the default method, according to the transmission protocol on which the request message is based, obtaining the reserved resources for the service on the output port queue corresponding to the default priority carried in the request message; after searching for the service identifier carried in the service message in the second mapping relationship, it also includes: when the service identifier carried in the service message is not found in the second mapping relationship, obtaining the second target queue according to the protocol of the request message; the second target queue refers to the output port queue corresponding to the default priority carried in the service message; putting the service message into the target queue, and sending the service message based on the resources reserved at the target queue; the target queue is the first target queue or the target queue. That is, when a network device receives a service message, it first searches for an egress port queue based on the service identifier in the service message. When the egress port queue is found based on the service identifier in the service message, the message is sent according to the egress port queue corresponding to the default priority. This embodiment provides a method for searching for an egress port queue for which resources have been reserved for a service message. Service messages for which resources have been reserved in a default manner or in an extended manner can be sent by this device.

[0011] In addition, the request message is pre-configured with a first field for indicating the resource reservation method and a second field for indicating the extended priority. That is, the first field is specifically used to indicate the resource reservation method, and the second field is specifically used to indicate the extended priority. By using newly added fields in the request message to carry the resource reservation method and extended priority information, the proposed extended resource reservation method can be implemented without affecting the transmission of the request message and resource reservation using existing transmission protocols. Because it does not conflict with existing transmission protocols, it is relatively simple and flexible to implement.

[0012] In addition, obtaining a service identifier from a request message includes: extracting the value of a third field associated with the service identifier from the request message; obtaining the service identifier based on the value of the third field and a preset third mapping relationship; wherein the third mapping relationship refers to the mapping relationship between the value of the third field and the service identifier. Through the above means, the mapping relationship between the service identifier and the value of the third field is pre-stored and maintained locally in the network device, and the service identifier composed of different data can be extracted as needed, and the services can be flexibly distinguished to provide better resource reservation services. wherein, the length of the third field can be set as needed, that is, the third field can be set shorter, and a service identifier with a relatively large amount of data can be obtained through the mapping relationship between the service identifier and the value of the third field; thereby, the message length of the request message can be shortened, the processing efficiency of the request message can be improved, and the bandwidth overhead of the request message can be saved.

[0013] In addition, the request message is a TalkerAdvertise message, and the third field is the Reserved field. In the application scenario of the SRP protocol, the Reserved field or the newly added Indicate field is used in the TalkerAdvertise message to carry the first field indicating the resource reservation method and the second field indicating the extension priority, reducing the modification of the protocol message structure and improving the compatibility of bridge devices with the extended protocol.

[0014] In addition, the above-mentioned port resource reservation method also includes: sending a request message carrying a resource reservation request; before sending the request message carrying the resource reservation request, it also includes: receiving a detection message from the target node, and determining whether the target node supports a resource reservation method consistent with the priority information in the request message based on the detection message; wherein the priority information includes: extended priority and default priority; if the target node supports a resource reservation method consistent with the priority information in the request message, then executing the sending of the request message carrying the resource reservation request. Through the above-mentioned means, the detection message is also extended at the same time, so that it is possible to determine whether the device of the target node supports resource reservation in an extended manner through the detection message, thereby avoiding the modification of the standard process of the existing resource reservation protocol.

[0015] In addition, determining the resource reservation method supported by the target node based on the probe message includes: obtaining the fourth field in the probe message; wherein the fourth field is used to indicate the number of priority categories supported by the target node; comparing the length of the fourth field with the length of the second field in the request message; if the length of the fourth field is greater than or equal to the length of the second field, determining that the target node supports resource reservation in an extended manner; if the length of the fourth field is less than the length of the second field, determining that the target node does not support resource reservation in an extended manner. The length of the field in the probe message that records the number of supported priorities is extended so that the length of the field carrying the number of priorities in the probe message is consistent with the length of the field carrying the extended priority in the request message, and the existing protocol process can be used to detect the resource reservation method supported by the node. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] One or more embodiments are exemplarily described by the figures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments.

[0017] Figure 1 is a flow chart of a port resource reservation method according to a first embodiment of the present invention;

[0018] Figure 2 1 is a schematic diagram of the structure of a TalkerAdvertise message in the current SRP protocol according to the first embodiment of the present invention;

[0019] Figure 3 1 is a schematic diagram of the structure of the TalkerAdvertise message in the extended SRP protocol according to the first embodiment of the present invention;

[0020] Figure 4 1 is a schematic diagram of a mapping relationship between an X-tuple and an IPv according to a first embodiment of the present invention;

[0021] Figure 5 is a flow chart of a port resource reservation method according to a second embodiment of the present invention;

[0022] Figure 6 is a flow chart of a port resource reservation method according to a third embodiment of the present invention;

[0023] Figure 7 2 is a schematic diagram of the structure of a Domain Discovery message in the current SRP protocol according to the third embodiment of the present invention;

[0024] Figure 8 2 is a schematic diagram of the structure of the Domain Discovery message in the extended SRP protocol according to the fourth embodiment of the present invention;

[0025] Figure 9FIG. 5 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of this application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and various embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0027] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described can be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or precedence. The first embodiment of the present invention relates to a method for port resource reservation, which is applied to a bridge device. In this embodiment, a request message for reserving resources for a service is received, and a resource reservation mode is determined according to the request message; when it is determined that the resource reservation mode is an extended mode, the output port queue corresponding to the extended priority carried in the request message is obtained according to a preset first mapping relationship, and resources are reserved for the service on the output port queue corresponding to the extended priority; wherein the first mapping relationship refers to the correspondence between the extended priority and the output port queue; the service identifier is obtained from the request message, and a second mapping relationship is established; wherein the second mapping relationship refers to the mapping relationship between the service identifier and the extended priority.

[0028] This embodiment will be further described below with reference to the accompanying drawings.

[0029] The port resource reservation method in this embodiment is as follows Figure 1 As shown, specifically including:

[0030] Step 101: Receive a request message for reserving resources for a service, and determine a resource reservation method according to the message.

[0031] Specifically, the port resource reservation method in this embodiment is an extension of the existing resource reservation protocol. A request message is sent by the service sending end to the next node in the service transmission path, informing the next node to reserve appropriate bandwidth resources for the service to be received. The request message contains data indicating the resource reservation method to be used when the resource reservation protocol is running. The resource reservation protocol has two resource reservation methods: a default method and an extended method. After receiving the request message, the next node in the transmission path determines the current resource reservation method based on the data in the request message.

[0032] In a specific implementation, taking the SRP protocol as an example, the request message is a Talker Advertise message, and the message structure is as follows: Figure 2 As shown. In the Talker Advertise message, the default priority information is carried by the DataFramePriority field. The length of this field is 3 bits, and it can only support up to 8 priorities. During the operation of the protocol, since one priority needs to be reserved for the BE (Best Effort) service, it is actually only possible to support resource reservation on a maximum of 7 outbound port queues. In this embodiment, the existing field that carries priority information can be expanded. The specific means include but are not limited to adding a new field internal priority (Internal Priority Value, IPV) in the Talker Advertise message, that is, the above-mentioned extended priority, whose length is N bits, where N is a natural number greater than three, and the number of priorities supported is 2. n , the corresponding number of supported outbound port queues is 2 n-1 .

[0033] When a network device receives an extended Talker Advertise message, it can determine the current resource reservation method based on the value in the IPv field. If the IPv field value is in the range of 0 to 7, the IPv field is invalid and the default resource reservation method is still used for port resource reservation. If the IPv field value is greater than 7, the extended method is used for port resource reservation.

[0034] In one example, the resource reservation protocol takes the SRP protocol as an example, the request message is a Talker Advertise message, and the third field can be the Reserved field in the Talker Advertise message. The Reserved field is a blank field in the protocol standard, so this field can be used as the third field to store the relevant data indicating the service identifier. In addition, a new Indicate field can be added to the Talker Advertise message as the third field to store the relevant data indicating the service identifier. The structure of the expanded Talker Advertisement message is as follows: Figure 3 As shown, the newly added message content is located in the IPVAndIndication line, including an IPV field with a length of 16 bits and an Indicate field with a length of 8 bits.

[0035] In a specific implementation, a 1-bit data bit can be used as an indicator of the resource reservation mode. This 1-bit data bit can occupy a 1-bit length and be stored in the Reserved field of the Talker Advertise message or the newly added Indicate field. For example, the first bit of the Reserved field can be used as the indicator of the resource reservation mode. If the data in this bit is 0, it indicates that the resource reservation is still performed according to the default mode specified in the protocol. If the data in this bit is 1, it indicates that the resource reservation is performed according to the extended mode.

[0036] Step 102: Determine whether to use an extended method to reserve resources.

[0037] When it is determined according to the service message that resources are currently reserved in a default manner, the resource reservation process is consistent with the standard process of the current resource reservation protocol, and step 113 to step 114 are executed.

[0038] Step 113: According to the transmission protocol on which the request is based, obtain the outbound port queue corresponding to the default priority carried in the request message.

[0039] Specifically, the transmission protocol takes the SRP protocol as an example. The DataFramePriority field in the request message carries the default priority information. The corresponding relationship between the default priority recommended in the protocol and the outbound port queue is shown in the following table:

[0040]

[0041] In actual applications, in addition to determining the egress queue (Traffic Class) for reserved resources based on the correspondence in the above table, the user may also pre-set a personalized correspondence between the default priority and the egress queue based on demand.

[0042] Step 114: reserve resources for the service on the outbound port queue corresponding to the default priority.

[0043] Specifically, the transmission protocol takes the SRP protocol as an example. The DataFramePriority field is used in the request message to carry the default priority information. After the priority is determined according to the DataFramePriority field, resources are reserved on the output port corresponding to the priority according to the mapping relationship between the preset priority and the output port queue.

[0044] When it is determined according to the service message that resource reservation is currently being performed in an extended manner, step 102 is executed.

[0045] Step 103: According to a preset first mapping relationship, the outbound port queue corresponding to the extended priority carried in the request message is obtained.

[0046] IPV TrafficClass 8 5 9 7 10 9 11 10 12 11 13 12 14 13

[0047] In actual applications, the field length can be set appropriately based on current needs, such as the number of ports on a bridge device, or a longer field can be set to maximize compatibility with bridge devices with different port counts on the same network. Assuming the currently set IPV field length is 8 bits, this means the IPV value can range from 0 to 256. After receiving the Talk Advertise message, the value of the IPV field is read. Because the extended IPV field still needs to be compatible with the default priority, resource reservation is performed using the default method when the priority is 0 to 7. Therefore, under the premise that the extended method has been determined for resource reservation, if the read IPV field value is between 0 and 7, it indicates that the resource reservation method and priority are incorrect, and resource reservation has failed.

[0048] Step 104: reserve resources for the service on the outbound port queue corresponding to the extended priority.

[0049] Specifically, after finding the egress queue corresponding to the extended priority, the required bandwidth resources are calculated according to the service characteristics carried in the request message and the bandwidth resources are reserved for the queue.

[0050] In a specific implementation, taking the SRP protocol as an example, the service characteristics are carried in the TSpec (Traffic Specification) field of the Talker Advertise message. The TSpec records the traffic parameters of the service.

[0051] Step 105: Obtain the service identifier from the request message and establish a second mapping relationship.

[0052] Specifically, the second mapping relationship refers to the mapping relationship between the service identifier and the extended priority. In the prior art, the priority field in the service message (such as the PCP field in the TSN message) is usually used directly to match the service message with the priority. Therefore, after obtaining the service message, the corresponding output port queue can be directly determined, so that the service message can be placed in the reserved output port queue. In this embodiment, since the number of priorities supported by the extended priority is greater than the number of priorities that can be recorded by the priority field in the relevant technology, the service identifier can be obtained according to the request message. The service identifier may include the priority field, and may also include specific service information such as the virtual local area network identifier VLANID, the target address IP, etc. Combining these service information can distinguish a larger number of service categories, thereby subdividing the service types and providing fine-grained resource reservation services.

[0053] A second mapping relationship is established between the service identifier and the extended priority. The purpose is to search for the priority information corresponding to the service message in the second mapping relationship based on the service identifier carried in the service message when a subsequent service message is received, so as to place the service message in the reserved outbound port queue and complete the service scheduling process.

[0054] Furthermore, the service identifier is determined by the third field carried in the request message. First, the value of the third field associated with the service identifier is extracted from the request message. Then, the service identifier is obtained based on the value of the third field and a preset third mapping relationship. The third mapping relationship refers to the mapping relationship between the third field value and the service representation.

[0055] In one specific implementation, the service identifier is a message X-tuple consisting of X field values in the service message, where X is a natural number greater than 1. The fields in the service message that specifically comprise the X-tuple are determined by the third field and the third mapping relationship, and each value of the third field corresponds to a field composition of the X-tuple.

[0056] In an example, the value of the third field and the field composition of the X-tuple are shown in the following table:

[0057] The third field value The fields of the X tuple are: 1 {SrcMac,PCP,DestMulticastMac,VlanID} 2 {DestMultiCastMac,VlanID,PCP} 3 {SrcMac,VlanID} … …

[0058] Assuming that bits 2 to 4 (a total of 3 bits) of the Reserved field (or Indicate field) are currently used to store data related to the service identifier, eight methods can be used to determine the content of the X-tuple. If the value is 0, it means that the 3-tuple {SrcMac, destMulticastMac, VlanID} in the packet header is used as the TSN traffic identification mark when searching for the corresponding IPv. A value of 1 indicates that the X-tuple {SrcMac, PCP, DestMulticastMac, VlanID} in the packet header is used as the identifier for TSN service packets. If the value is 2, the X-tuple is {DestMultiCastMac, VlanID, PCP}. If the value is 3, the X-tuple is {SrcMac, VlanID}, and so on.

[0059] After determining the X-tuple from the Talker Advertise message, a mapping relationship between the X-tuple and the IPv is established. The specific mapping method is as follows: Figure 4 As shown:

[0060] Among them, node 1 (Stream1Talker) is the first service sending node, and sends a TalkerAdvertise message to node 4 (Stream1Listener) through node 3. The X tuple carried in the message is {01:00:5e:00:01:00,500,2} ({destination address Destination, virtual local area network identifier VLANID, internal data priority DataFramePriority}), and the IPv is 10. Then, node 4 establishes a mapping relationship between the X tuple and the IPv based on the data in the message; node 2 (Stream1Talker) is the second service sending node, and the X tuple carried in the message is {01:00:5e:00:01:00,100} ({Destination, VLANID}) and the IPv is 11. It sends a TalkerAdvertise message to node 5 (Stream1Listener) through node 3, and then node 4 establishes a mapping relationship between the X tuple and the IPv based on the data in the message. The second mapping relationship established by node 4 and node 5 is shown in the figure. Since both service 1 and service 2 pass through node 3, the second mapping relationship established by node 3 based on the TalkerAdvertise messages of service 1 and service 2 is shown in the following table:

[0061] X-tuple IPV {01:00:5e:00:01:00,500,2} 10 {01:00:5e:00:01:01,100} 11

[0062] In actual applications, after the above-mentioned node 4 or node 5 establishes the X-tuple-IPV mapping relationship according to the TalkerAdvertise message, it can use the IEEE 802.1Qci component to implement the maintenance of the mapping table, as shown in the following table:

[0063]

[0064] The SRP extension configures two FilterInstance entries in the FilterInstanceTable, with IDs 1 and 2. The StreamHandle for FilterInstanceID 1 is {DestMulticastMac,VLANID,pcp} = {01:00:5e:00:01:00,500,2}, and the StreamHandle for FilterInstanceID 2 is {DestMulticastMac,VLANID} = {01:00:5e:00:01:01,100}. The GateInstanceTable IDs for these two FilterInstance entries are 1 and 2, respectively. The SRP extension configures two entries in the GateInstanceTable with IDs 1 and 2. The gate states of these two entries are always "0," and the IP addresses are 10 and 11, respectively. The above configuration indicates that TSN packets whose packet headers match the entry with FilterInstanceID 1 are mapped to IP address 10, while packets matching the entry with FilterInstanceID 2 are mapped to IP address 11.

[0065] It should be noted that the above examples in this embodiment are only illustrative for ease of understanding and do not limit the technical solutions of the present invention.

[0066] Compared with the prior art, this embodiment extends the existing resource reservation method while retaining the original resource reservation method. When a request message is received to reserve resources for a service, if it is determined based on the request message that the extended method is currently used for resource reservation, the output port queue corresponding to the extended priority carried in the request message is found based on a preset mapping relationship; then the service identifier of the service is obtained from the request message, and a mapping relationship between the service identifier and the extended priority is established. Priority and output port queue have a one-to-one correspondence, and the number of categories supported by the extended priority is much higher than the number of categories supported by the priority in the prior art, thereby making full use of the port resources in the bridge device to provide fine-grained port resource reservation services for service messages.

[0067] The second embodiment of the present invention relates to a port resource reservation method. The present embodiment will be described in detail below with reference to the accompanying drawings. The port resource reservation method in the present embodiment is as follows: Figure 5 As shown, including:

[0068] Step 501: Receive a request message for reserving resources for a service, and determine a resource reservation method according to the request message.

[0069] This step is the same as step 101 in the first embodiment of the present invention. The relevant implementation details have been described in detail in the first embodiment of the present invention and will not be repeated here.

[0070] Step 502 , determining whether to use an extended method to reserve resources. If the extended method is used to reserve resources, executing steps 513 to 515 .

[0071] Specifically, the method steps for resource reservation using the extended mode are steps 513 to 515. Steps 513 to 515 are the same as steps 102 to 104 in the first embodiment of the present invention. The relevant implementation details have been described in detail in the first embodiment of the present invention and will not be repeated here.

[0072] If the default method is used for resource reservation, step 523 to step 524 are executed.

[0073] Step 523: According to the transmission protocol on which the request is based, obtain the outbound port queue corresponding to the default priority carried in the request message.

[0074] Step 524: Reserve resources for the service on the outbound port queue corresponding to the default priority.

[0075] Step 523 and Step 524

[0076] Step 516: Receive a service message, and search the second mapping relationship for the service identifier carried in the service message.

[0077] Step 517, determine whether the service identifier carried in the service message is found; if the service identifier carried in the service message is found, it means that the service is reserved according to the extended method, then execute steps 518 to 519; if the service identifier carried in the service message is not found, it means that the service is reserved according to the default method, then execute steps 525 to 526.

[0078] Step 518: Obtain the first target queue according to the second mapping relationship and the first mapping relationship.

[0079] Step 519: Put the service message into the first target queue, and send the service message based on the resources reserved at the target queue.

[0080] Specifically, in existing resource reservation protocols, when a service is transmitted in a network and forwarded from one node to the next, the sending node first sends a request message to the next node on the service forwarding path, instructing the next node to reserve bandwidth resources on the port for the service. In this embodiment, when a service message arrives at a node, the node that has already reserved resources extracts the service identifier from the service message and then searches for the service identifier in a second mapping relationship. If the service identifier exists in the second mapping relationship, it indicates that resources have been pre-reserved for the service in an extended manner. The extended priority of the service is determined based on the second mapping relationship between the service identifier and the extended priority. Then, the egress port queue corresponding to the extended priority is determined based on the preset first mapping relationship, and the service message is placed in the egress port queue for forwarding using the pre-reserved bandwidth resources.

[0081] In a specific implementation, the service message takes the TSN message as an example, and the service identifier is the X-tuple extracted in step 104 mentioned in the first embodiment of the present invention. The TSN message also carries multiple fields in the X-tuple, which are located at the beginning of the message, that is, the header field. Therefore, after receiving the TSN message, the network device will first search the second mapping relationship, that is, the second mapping relationship between the X-tuple and the IPV priority, to see whether there is a header field value carried by the TSN message. If there is a header field value carried by the TSN message, the IPV priority corresponding to the X-tuple is determined according to the second mapping relationship, and then the output port queue of the reserved resources is further determined according to the mapping relationship between the IPV priority and the output port queue, and the TSN service message is placed in the output port queue for transmission.

[0082] Step 525: Obtain a second target queue according to the service message.

[0083] Step 526: Put the service message into the second target queue, and send the service message based on the resources reserved at the second target queue.

[0084] Specifically, if the service identifier carried in the service message is not found, it means that the service is reserved according to the default method, and then the outbound port queue corresponding to the priority field is directly determined according to the field carrying priority information in the service message.

[0085] In an example, assume that there are 9 service flows in the current TSN network environment, as shown in the following table:

[0086] StreamID Traffic type Class_Measure_Interval Delay upper bound requirement 1 ISOchronous-Cyclicreal-time 5us 1ms 2 Cyclic real-time 10us 2ms 3 Network control 15us 3ms 4 Audio / video 125us 50ms 5 brownfield 200us 100ms 6 Alarms / events 300us 10ms 7 Configuration / diagnostics 100us 5ms 8 Internal / pass-through 500us 10ms 9 Best-effort N / A N / A

[0087] All network devices run the SRP protocol. Each service flow has different traffic types, class_measure_intervals, and latency limits. Service flows 1 through 8 are deterministic and require SRP to allocate bandwidth resources. These eight types of traffic have different quality of service (QoS) and service level (GSL) requirements.

[0088] If the current SRP protocol is used, these eight types of traffic will be assigned to the same SR Class and priority for service. However, the current SRP protocol only supports a maximum of seven SR Class categories, which means that at least two service flows must be forcibly assigned to the same priority for service. For example, the internal data priority DataFramePriority of the 7th and 8th traffic flows is both 7, as shown in the following table:

[0089] StreamID SR ClassID DataFramePriority 1 A 2 2 B 3 3 C 1 4 D 4 5 E 5 6 F 6 7 G (7) 8 G (7) 9 N / A N / A

[0090] If the extended SRP protocol proposed in this embodiment is adopted, after receiving the TalkerAdvertise message of the service traffic, each network node network device reserves resources according to the IPv field added in the message. It can allocate its own SR Class and internal priority IPv for each service with different network service requirements, thereby providing more fine-grained services, as shown in the following table:

[0091] StreamID SR ClassID IPV TrafficClass 1 8 8 8 2 9 9 9 3 10 10 10 4 11 11 11 5 12 12 12 6 13 13 13 7 14 14 14 8 15 15 15 9 N / A N / A 16

[0092] StreamID is the service ID, SR ClassID is the priority identifier, IPV is the extended priority, and TrafficClass is the queue number of the corresponding egress port for resource reservation.

[0093] The steps of the various methods above are divided only for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0094] Compared with the prior art, this embodiment enables the expanded resource reservation method to still be compatible with the default resource reservation method in the prior art, and can still provide normal port resource reservation service when receiving a request message carrying a default priority.

[0095] The third embodiment of the present invention relates to a port resource reservation method, which is roughly the same as the second embodiment of the present invention, with the difference being that: in this embodiment, in addition to expanding the structure of the request message and the method of reserving business resources, the premise for resource reservation, namely, the detection message in the network domain boundary detection, is also expanded, but this extension does not affect the specific working process of the domain boundary detection.

[0096] This embodiment will be further described below with reference to the accompanying drawings.

[0097] The domain boundary detection process in this embodiment is as follows Figure 6 As shown, specifically including:

[0098] Step 601: Receive a detection message from a target node.

[0099] Specifically, the detection message sent by the target node carries the number of priorities and port queues supported by the target node. The node in the network that is about to send the service will determine whether to send the service to the target node based on the detection message sent by the target node.

[0100] Step 602: Determine the resource reservation method supported by the target node based on the detection message and judge whether it supports extended method for resource reservation. If it supports extended method for resource reservation, execute step 603; if it does not support extended method for resource reservation, execute step 601 and receive the detection message from the target node.

[0101] Specifically, resource reservation in an extended manner can support more types of priorities and port queue numbers. Therefore, when a node that supports resource reservation in an extended manner sends a service message, it is necessary to determine whether the next node on the traffic path, that is, the target node, supports resource reservation in an extended manner. If the target node supports resource reservation in an extended manner, a request message carrying a resource reservation request is sent to the target node; if not, it continues to accept detection messages from other target nodes.

[0102] Furthermore, when a detection message is obtained from the target node, the fourth field in the detection message is first obtained to indicate the number of priority categories supported by the target node. The length of the fourth field is then compared with the length of the second field in the request message. Since the maximum value that a field can represent in the message is limited by the length occupied by the field, the maximum number of priorities that can be represented in the detection message and the number of priority categories in the second field can be compared based on the field length. In other words, if the length of the fourth field is greater than or equal to the length of the second field, it is determined that the target node supports resource reservation in an extended manner; if the length of the fourth field is less than the length of the second field, it is determined that the target node does not support resource reservation in an extended manner.

[0103] In a specific implementation, taking the Domain Discovery message for domain boundary detection in the SRP protocol as an example, the structure of the Domain Discovery message in the prior art is as follows: Figure 7 As shown, the structure of the extended Domain Discovery message is as follows Figure 8 As shown. In the Domain Discovery message before extension, the length of the SRClassID and SRClassPriority fields are both 8 bits, indicating that a Domain Discovery message can represent a maximum of 256 priority levels. In order to match the length of the IPV field mentioned in the first embodiment of the present invention, the length of the SRClassID and SRClassPriority fields in the Domain Discovery message after extension is extended to 16 bits, which is the same as the number of priorities that the IPV field can support.

[0104] The relevant technical details mentioned in the first and second embodiments are still valid in this embodiment, and the technical effects achieved in the second embodiment can also be achieved in this embodiment. To reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the first and second embodiments.

[0105] A fourth embodiment of the present invention relates to an electronic device, such as Figure 9 As shown, it includes at least one processor 901; and, at least one memory 902; wherein, the memory 902 stores instructions that can be executed by the at least one processor 901, and the instructions are executed by the at least one processor 901 to enable the at least one processor 901 to execute the port resource reservation method in the first, second, or third embodiment.

[0106] The memory 902 and processor 901 are connected using a bus. The bus may include any number of interconnected buses and bridges, connecting various circuits of one or more processors 901 and memory 902. The bus may also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits. These are all well known in the art and are therefore not described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be a single component or multiple components, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor 901 is transmitted over a wireless medium via an antenna. Furthermore, the antenna receives data and transmits it to the processor 901.

[0107] The processor 901 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 902 can be used to store data used by the processor 901 when performing operations.

[0108] A fifth embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0109] That is, those skilled in the art will understand that all or part of the steps in the above method embodiments can be implemented by instructing the relevant hardware through a program, which is stored in a storage medium and includes a number of instructions for causing a device (which may be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps in the various embodiments of the present application. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., various media that can store program code.

[0110] Those skilled in the art will appreciate that the above are specific embodiments for implementing the present invention, and that in actual applications, various changes may be made in form and details without departing from the spirit and scope of the present invention.

Claims

1. A port resource reservation method, characterized in that: include: receiving a request message for reserving resources for a service, and determining a resource reservation method according to the request message; When it is determined that the resource reservation mode is the extended mode, obtaining, according to a preset first mapping relationship, an egress port queue corresponding to the extended priority carried in the request message, and reserving resources for the service on the egress port queue corresponding to the extended priority; wherein the first mapping relationship refers to a mapping relationship between the extended priority and the egress port queue, and wherein the extended mode refers to a resource reservation mode implemented by using the extended priority field; Obtaining a service identifier from the request message and establishing a second mapping relationship; wherein the second mapping relationship refers to a mapping relationship between the service identifier and the extended priority, and the second mapping relationship is used to determine corresponding extended priority information based on the service identifier carried in a subsequent service message received, so as to place the service message into an outbound port queue pre-reserved based on the extended priority; After obtaining the service identifier from the request message and establishing the second mapping relationship, the method further includes: receiving a service message, and searching the second mapping relationship for a service identifier carried in the service message; When the service identifier carried in the service message is not found in the second mapping relationship, obtaining a second target queue according to the transmission protocol based on the request message; the second target queue is an egress port queue corresponding to the default priority carried in the service message; The service message is placed in the second target queue, and the service message is sent based on the resources reserved at the second target queue.

2. The port resource reservation method according to claim 1, wherein: After receiving the service message and searching the second mapping relationship for the service identifier carried in the service message, the method further includes: When the service identifier carried in the service message is found in the second mapping relationship, a first target queue is obtained according to the second mapping relationship and the first mapping relationship; the first target queue is the outbound port queue corresponding to the service identifier carried in the service message; The service message is placed in the first target queue, and the service message is sent based on the resources reserved at the first target queue.

3. The port resource reservation method according to claim 2, characterized in that: After determining the resource reservation method according to the request message, the method further includes: When it is determined that the resource reservation method is the default method, according to the transmission protocol on which the request message is based, the output port queue corresponding to the default priority carried in the request message is obtained, and resources are reserved for the service on the output port queue corresponding to the default priority, wherein the default method refers to a method of reserving resources based on the default priority field in the existing protocol.

4. The port resource reservation method according to claim 1, wherein: The request message is preset with a first field for indicating the resource reservation mode and a second field for indicating the extended priority.

5. The port resource reservation method according to claim 1, characterized in that: The obtaining of the service identifier from the request message includes: Extracting a value of a third field associated with the service identifier from the request message; The service identifier is obtained according to the value of the third field and a preset third mapping relationship; wherein the third mapping relationship refers to a mapping relationship between the value of the third field and the service identifier.

6. The port resource reservation method according to claim 5, characterized in that: The request message is a TalkerAdvertise message in the stream reservation protocol SRP, and the third field is a Reserved field.

7. The port resource reservation method according to claim 2, characterized in that: Before placing the service message into the first target queue and sending the service message based on the resources reserved at the first target queue, the method further includes: receiving a detection message from a target node, and determining a resource reservation mode supported by the target node according to the detection message; If the resource reservation mode supported by the target node includes the extended mode, sending the request message to the target node; The step of placing the service message into the first target queue and sending the service message based on the resources reserved at the first target queue is specifically, placing the service message into the first target queue and sending the service message to the target node based on the resources reserved at the first target queue.

8. The port resource reservation method according to claim 7, characterized in that: The determining, according to the detection message, a resource reservation mode supported by the target node includes: The resource reservation method supported by the target node is determined according to the length of the fourth field in the detection message; wherein the fourth field is a field used to indicate the number of priorities supported by the target node, or the fourth field is a field used to indicate the service categories supported by the target node; wherein the number of service categories and priorities is the same and corresponds one to one.

9. A network device, characterized in that: include: at least one processor; as well as, at least one memory; wherein, The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to perform the port resource reservation method according to any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the port resource reservation method according to any one of claims 1 to 8 is implemented.

Images