WO2021208529A1 - 端口资源预留方法、电子设备及存储介质 - Google Patents

端口资源预留方法、电子设备及存储介质 Download PDF

Info

Publication number
WO2021208529A1
WO2021208529A1 PCT/CN2021/070267 CN2021070267W WO2021208529A1 WO 2021208529 A1 WO2021208529 A1 WO 2021208529A1 CN 2021070267 W CN2021070267 W CN 2021070267W WO 2021208529 A1 WO2021208529 A1 WO 2021208529A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
message
mapping relationship
resource reservation
field
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/070267
Other languages
English (en)
French (fr)
Inventor
朱向阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to ES21788443T priority Critical patent/ES3018109T3/es
Priority to EP21788443.6A priority patent/EP4087315B1/en
Priority to US17/759,888 priority patent/US12273276B2/en
Publication of WO2021208529A1 publication Critical patent/WO2021208529A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
    • H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority

Definitions

  • the present invention relates to the field of communication technology, in particular to a method, electronic equipment and storage medium for port resource reservation.
  • the IEEE 802.1Qat standard proposed by the IEEE provides a network stream reservation protocol SRP (Stream Reservation Protocol).
  • SRP Stream Reservation Protocol
  • the SRP protocol is a distributed resource reservation protocol used for time-sensitive networks (Time Sensitive Networks).
  • TSN Network
  • the Talker Advertise message in the SRP protocol carries a 3-bit data structure priority field (Data Frame Priority).
  • Data Frame Priority a 3-bit data structure priority field
  • the SRP protocol reserves the resources of the egress queue based on the priority field, and the existing priority field with a length of 3 bits only supports a maximum of 7 categories. , Which means that it supports up to 7 outbound port queues for resource reservation, and the actual TSN service category is far greater than 7 categories.
  • the number of outbound port queues supported by the bridge device is greater than 8, based on the current SRP The protocol cannot make full use of the outgoing port queue resources supported by the bridge device to meet the actual needs of TSN services.
  • the purpose of the embodiments of the present invention is to provide a port resource reservation method, electronic equipment and storage medium, which can provide fine-grained resource allocation services for services.
  • an embodiment of the present invention provides a method for reserving port resources, including: receiving a request message for reserving resources for a service, and according to the request The message determines the resource reservation mode; when it is determined that the resource reservation mode is the extended mode, the outgoing port queue corresponding to the extended priority carried in the request message is obtained according to the preset first mapping relationship, and the extended priority Resources are reserved for services on the corresponding egress port queue; among them, the first mapping relationship refers to the corresponding relationship between the extended priority and the egress port queue; the service identifier is obtained from the request message, and the second mapping relationship is established; The second mapping relationship refers to the mapping relationship between the service identifier and the extended priority.
  • An embodiment of the present invention also provides an electronic device, including: at least one processor; and, at least one memory; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to At least one processor can execute the port resource reservation method as described above.
  • the embodiment of the present invention also provides a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, the method for reserving port resources as described above is implemented.
  • Fig. 1 is a flowchart of a method for reserving port resources in a first embodiment of the present invention
  • FIG. 2 is a schematic diagram of the structure of TalkerAdvertise message in the current SRP protocol according to the first embodiment of the present invention
  • FIG. 3 is a schematic diagram of the structure of TalkerAdvertise message in the extended SRP protocol according to the first embodiment of the present invention
  • Figure 4 is a schematic diagram of a network device establishing a mapping relationship between X-tuples and IPV in the first embodiment of the present invention
  • Fig. 5 is a flowchart of a method for reserving port resources according to a second embodiment of the present invention.
  • Fig. 6 is a flowchart of a method for reserving port resources according to a third embodiment of the present invention.
  • FIG. 7 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.
  • FIG. 8 is a schematic diagram of the structure of a Domain Discovery message in the extended SRP protocol according to the fourth embodiment of the present invention.
  • Fig. 9 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
  • the first embodiment of the present invention relates to a method for port resource reservation, which is applied to a bridge device.
  • a request message for reserving resources for a service is received, and the resource reservation is determined according to the request message.
  • the outgoing port queue corresponding to the extended priority carried in the request message is obtained according to the preset first mapping relationship, and the outgoing port queue corresponding to the extended priority is obtained.
  • the first mapping relationship refers to the corresponding relationship between the extended priority and the outgoing port queue
  • the service identifier is obtained from the request message
  • the second mapping relationship is established; wherein, the second mapping relationship refers to The mapping relationship between service identification and expansion priority.
  • the extension carried in the request message is found according to the preset mapping relationship.
  • the outgoing port queue corresponding to the priority; then the service ID of the service is obtained from the request message, and the mapping relationship between the service ID and the extended priority is established. That is, in this embodiment, an expansion method is proposed during resource reservation.
  • the first mapping relationship between the expansion priority and the egress port queue is preset, and the service is established for the service according to the service identifier and the expansion priority in the request message.
  • the second mapping relationship between the identifier and the extended priority; through the first mapping relationship and the second mapping relationship, the mapping relationship between the service identifier, the extended priority, and the egress port queue is determined for the service; through this extension method, Based on the existing message transmission protocol, the number of priorities that can be supported in resource allocation can be expanded, so that the outgoing port queue resources in the network equipment can be fully utilized to provide fine-grained port resource prediction for service messages. Stay for service.
  • the port resource reservation method in this embodiment is shown in Figure 1, and specifically includes:
  • Step 101 Receive a request message for reserving resources for a service, and determine a resource reservation mode according to the message.
  • the port resource reservation method in this embodiment is an extension of the existing resource reservation protocol.
  • the request message is sent by the service sender to the next node of the service transmission path to notify the next node to reserve suitable bandwidth resources for the service to be received.
  • the request message contains data used to indicate the resource reservation mode when the resource reservation protocol is running.
  • the resource reservation protocol has two resource reservation modes, including: the default mode and the extended mode. After receiving the request message, the next node in the above transmission path determines the current resource reservation mode according to the data in the request message.
  • the request message is a Talker Advertise message, and the message structure is shown in Figure 2.
  • the Talker Advertise message the default priority information is carried through the DataFramePriority field.
  • the length of this field is 3 bits (bits), and only 8 priority levels can be supported at most.
  • the existing bearer priority information field can be extended.
  • the specific methods include but are not limited to adding a new field internal priority (IPV) to the Talker Advertise message, that is, the above-mentioned extended priority.
  • IPV new field internal priority
  • the length of the level is N bit, where N is a natural number greater than three, the number of priority levels supported is 2 n , and the corresponding number of egress port queues supported is 2 n-1 .
  • the network device When the network device receives the extended Talker Advertise message, it can determine the currently adopted resource reservation method according to the value in the IPV field. Among them, if the value of the IPV field is in the range of 0 to 7, the IPV field is in an invalid state, and the default resource reservation method is still used for port resource reservation; if the value of the IPV field is greater than 7, then Use the expansion method to reserve port resources.
  • the resource reservation protocol takes the SRP protocol as an example
  • the request message is a Talker Advertise message
  • the third field can be the Reserved field in the Talker Advertise message.
  • the Reserved field is a blank field in the protocol standard. Therefore, this field can be used as the third field to store relevant data indicating the service identification.
  • a new Indicate field can be added to the Talker Advertise message as the third field to store relevant data indicating the service identifier.
  • the structure of the extended Talker Advertise message is shown in Figure 3.
  • 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.
  • 1 bit of data can also be used as an indicator of the resource reservation mode.
  • This 1 bit of data can occupy a length of 1 bit and be stored in the Reserved field of the Talker Advertise message or the newly added Indicate field.
  • the first bit of the Reserved field is used as an indicator of the resource reservation mode. If the data of this bit is 0, it means that the resource reservation is still carried out according to the default mode specified in the agreement. If the data of this bit is 1 , It means to reserve resources according to the expansion mode.
  • a first field for indicating a resource reservation mode and a second field for indicating an extended priority are preset in the request message. That is, the first field is specifically used to indicate the resource reservation mode, and the second field is specifically used to extend the priority; in the request message, the information of the resource reservation mode and the information of the extended priority are carried in the form of newly added fields. It can realize the resource reservation proposed in this application in an extended manner without affecting the transmission of the request message by the existing transmission protocol and the resource reservation; since it does not conflict with the existing transmission protocol, it is realized It is simpler and more flexible.
  • the request message is a TalkerAdvertise message
  • the third field is a Reserved field.
  • the Reserved field or the newly added Indicate field is used in the TalkerAdvertise message to carry the first field indicating the resource reservation mode and the second field indicating the extended priority, reducing the need for protocol messages.
  • the modification of the structure improves the compatibility of the bridge equipment with the extended protocol.
  • Step 102 Determine whether to use an extended mode for resource reservation.
  • the resource reservation process is consistent with the standard process of the current resource reservation protocol, and step 113 to step 114 are performed.
  • 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.
  • the transmission protocol uses the SRP protocol as an example
  • the request message carries the default priority information through the DataFramePriority field
  • the correspondence between the default priority recommended in the protocol and the outgoing port queue is shown in the following table:
  • the user in addition to determining the outbound port queue (Traffic Class) of reserved resources according to the corresponding relationship in the above table; in addition, the user can also set the personalized default priority and outbound port queue according to requirements in advance. Correspondence.
  • Step 114 Reserve resources for the service on the outgoing port queue corresponding to the default priority.
  • the transmission protocol uses the SRP protocol as an example.
  • the request message uses the DataFramePriority field to carry default priority information. After the priority is determined according to the DataFramePriority field, according to the preset mapping relationship between the priority and the outgoing port queue, Resource reservation is performed on the outgoing port corresponding to the priority.
  • step 102 is executed.
  • Step 103 Obtain the egress port queue corresponding to the extended priority carried in the request message according to the preset first mapping relationship.
  • Step 104 Reserve resources for the service on the outgoing port queue corresponding to the extended priority.
  • the required bandwidth resource is calculated according to the service characteristics carried in the request message and the bandwidth resource is reserved on the queue.
  • the service characteristics are carried in the TSpec (Traffic Specification) field of the Talker Advertise message, and the TSpec records the traffic parameters of the service.
  • TSpec Traffic Specification
  • Step 105 Obtain the service identifier from the request message, and establish a second mapping relationship.
  • the second mapping relationship refers to the mapping relationship between the service identifier and the extended priority.
  • the priority field in the service message (such as the PCP field in the TSN message) is usually directly used to match the service message with the priority. Therefore, after the service message is obtained, it can be directly determined Corresponding to the outgoing port queue, so that the service packets are put into the reserved outgoing port queue.
  • the service identification can be obtained according to the request message, and the service identification can include the priority field. It can also include specific business information such as virtual local area network identification VLANID, target address IP, etc. Combining these business information can distinguish a larger number of business categories, thereby subdividing business types, and providing fine-grained resource reservation service.
  • the second mapping relationship is established between the service identifier and the extended priority.
  • the purpose is to find the service report in the second mapping relationship according to the service identifier carried in the service message when a subsequent service message is received. Priority information corresponding to the message, so that the service message is put into the reserved out port queue to complete the service scheduling process.
  • the service identifier is determined by the third field carried in the request message. First, extract the value of the third field associated with the service ID from the request message, and then obtain the service ID according to the value of the third field and the preset third mapping relationship.
  • the third mapping relationship refers to the mapping relationship between the value of the third field and the service representation.
  • the length of the third field can be set as required, that is, the third field can be set to be shorter, and the 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; thus, it can be shortened
  • the message length of the request message improves the processing efficiency of the request message and saves the bandwidth overhead of the request message.
  • the service identifier is a message X tuple composed of field values in X service messages, where X is a natural number greater than 1.
  • X is a natural number greater than 1.
  • the value of the third field and the field composition of the X-tuple are shown in the following table:
  • the value is 0, it means that the 3-tuple ⁇ SrcMac, destMulticastMac, VlanID ⁇ in the header is used as the TSN traffic identification mark when searching for the corresponding IPV.
  • the X tuple ⁇ SrcMac,PCP,DestMulticastMac, VlanID ⁇ is used as the identifier for TSN service message identification.
  • the value is 2
  • the X-tuple is ⁇ DestMultiCastMac, VlanID, PCP ⁇
  • the value is 3, the X-tuple is ⁇ SrcMac, VlanID ⁇ , etc.
  • node 1 (Stream1Talker) is the No. 1 service sending node, and the TalkerAdvertise message is sent to node 4 (Stream1Listener) through node 3, and the X tuple carried in the message is ⁇ 01:00:5e:00:01:00,500 ,2 ⁇ ( ⁇ Destination address, virtual local area network identification VLANID, internal data priority DataFramePriority ⁇ ), IPV is 10, and then node 4 establishes the X-tuple-IPV mapping relationship according to the data in the message; node 2 (Stream1Talker) It is the No.
  • the X tuple carried in the message is ⁇ 01:00:5e:00:01:00,100 ⁇ ( ⁇ Destination, VLANID ⁇ ), and the IPV is 11, passing through node 3 to node 5 (Stream1Listener ) Send a TalkerAdvertise message, and then node 4 establishes the X-tuple-IPV mapping relationship according to the data in the message.
  • the second mapping relationship established by node 4 and node 5 has been shown in the figure; since both the first service and the second service pass through the node 3, the node 3 is based on the TalkerAdvertise message of the first service and the second service.
  • the second mapping relationship established is shown in the following table:
  • the IEEE 802.1Qci component can be used to maintain the mapping table, as shown in the following table:
  • the entry IDs are 1 and 2
  • the GateInstanceTable IDs corresponding to the two FilterInstance entries are 1 and 2, respectively
  • SRP extension The protocol configures two entries with IDs 1 and 2 in the GateInstanceTable.
  • the gate status of the two entries is always "O", and the IPV is 10 and 11 respectively.
  • the above configuration shows that the TSN packet whose header matches the table entry with FilterInstanceID 1 is mapped to IPV 10, and the packet whose header matches the table entry with FilterInstanceID of 2 is mapped to IPV 11.
  • the existing resource reservation method is expanded, and the original resource reservation method is retained at the same time.
  • a request message for reserving resources for the business is received, if it is determined that the current extension mode is used for resource reservation according to the request message, the corresponding extension priority carried in the request message is found according to the preset mapping relationship
  • the outbound port queue then obtain the service ID of the service from the request message, and establish the mapping relationship between the service ID and the extended priority.
  • Priority and outbound port queues have a one-to-one correspondence, and the number of categories supported by extended priority is much higher than the number of categories supported by priority in the prior art, so that the port resources in the bridge device can be fully utilized.
  • the second embodiment of the present invention relates to a port resource reservation method. This embodiment will be described in detail below with reference to the accompanying drawings.
  • the port resource reservation method in this embodiment is shown in FIG. 5 and includes:
  • Step 501 Receive a request message for reserving resources for the service, and determine a resource reservation mode according to the request message.
  • step 101 is the same as step 101 in the first embodiment of the present invention, and the relevant implementation details have been described in detail in the first embodiment of the present invention, and will not be repeated here.
  • step 502 it is determined whether the resource reservation is performed in the extended mode, and if the resource reservation is performed in the extended mode, step 513 to step 515 are performed.
  • step flow of the method for resource reservation in an extended manner is step 513 to step 515.
  • Steps 513 to 515 are the same as steps 102 to 104 in the first embodiment of the present invention, and the relevant implementation details have been described in detail in the first embodiment of the present invention, and will not be repeated here.
  • step 523 to step 524 are executed.
  • Step 523 According to the transmission protocol on which the request is based, obtain the outgoing port queue corresponding to the default priority carried in the request message.
  • Step 524 Reserve resources for the service on the outgoing port queue corresponding to the default priority.
  • Step 516 Receive the service message, and search for the service identifier carried in the service message in the second mapping relationship.
  • 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 resource reservation based on the extended mode, then step 518 to step 519 are performed; ; If the service identifier carried in the service message is not found, it means that the service is resource reservation performed according to the default mode, and then step 525 to step 526 are performed.
  • Step 518 Obtain the first target queue according to the second mapping relationship and the first mapping relationship.
  • 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.
  • the sending node when a service is transmitted on the network and is forwarded from one node to the next node, the sending node first sends a request message to the next node on the service forwarding path. Used to instruct the next node to reserve bandwidth resources on the port for this service.
  • the node that has reserved resources will extract the service identifier in the service message, and then search for the service identifier in the second mapping relationship.
  • the service identifier indicates that the service is pre-reserved in an extended manner, and the extension priority of the service is determined according to the second mapping relationship between the service identifier and the extension priority, and then determined according to the preset first mapping relationship
  • the egress port queue corresponding to the extended priority is put into the egress port queue and forwarded with the bandwidth resource reserved in advance.
  • This embodiment provides a way to find the corresponding egress port queue for the received service message after reserving resources in the egress port queue based on the extended method; that is, the service identifier is preset in the service message, so that it can be based on the first
  • the first mapping relationship and the second mapping relationship determine the outgoing port queue of the service packet. Due to the larger number of priorities, it can correspond to more outbound port queues and improve the utilization efficiency of port resources.
  • 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 the X-tuple. These fields are located at the beginning of the message, which is the header field. Therefore, after the network device receives the TSN message, it first searches for the value of the header field carried in the TSN message in the second mapping relationship, that is, the second mapping relationship between the X-tuple and the IPV priority.
  • Step 525 Acquire the second target queue according to the service message.
  • 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.
  • the service identifier carried in the service message is not found, it means that the service is reserved according to the default method. Then the priority is determined directly according to the field carrying priority information in the service message. The outgoing port queue corresponding to the field.
  • each network device runs SRP protocol.
  • Each service traffic has different traffic types, class_measure_interval, and delay upper bound requirements.
  • the first to eight business flows are deterministic business flows, and the SRP protocol is required to allocate bandwidth resources for them. These eight types of flows have different requirements for network service quality and service levels.
  • the current SRP protocol If the current SRP protocol is adopted, these eight types of traffic will be allocated to the same SR Class and priority to provide services, while the current SRP protocol only supports a maximum of 7 SR Class categories, which means that at least two service streams need to be forcibly divided into the same SR Class.
  • a priority provides services.
  • the internal data priority DataFramePriority of the 7th and 8th traffic is 7 as shown in the following table:
  • each network node network device After receiving the TalkerAdvertise message of the business traffic, each network node network device reserves resources according to the IPV field added in the message, and then it can reserve resources for each message. Services required by different network services are assigned their own SR Class and internal priority IPV to provide more fine-grained services, as shown in the following table:
  • StreamID is the service number
  • SR ClassID is the priority identifier
  • IPV is the extended priority
  • TrafficClass is the outbound port queue number corresponding to resource reservation.
  • the expanded resource reservation method is still compatible with the default resource reservation method in the prior art, and can still provide a normal port resource reservation service when a request message carrying a default priority is received.
  • a network device receives a service message, it first searches the outgoing port queue according to the service identifier in the service message. When searching for the outgoing port queue based on the service identifier in the service message, it performs processing according to the outgoing port queue corresponding to the default priority.
  • Send This embodiment provides a way to find outgoing port queues that have reserved resources for service messages. Service messages that reserve resources in a default mode or in an extended mode can all be sent on this device.
  • the third embodiment of the present invention relates to a method for reserving port resources. This embodiment is roughly the same as the second embodiment of the present invention.
  • the reservation method is expanded, and at the same time, the premise of resource reservation, that is, the detection message in the network domain boundary detection is expanded, but the expansion does not affect the specific working process of the domain boundary detection.
  • the domain boundary detection process in this embodiment is shown in Figure 6, and specifically includes:
  • Step 601 Receive a detection message from the target node.
  • the detection message sent by the target node carries the number of priorities supported by the target node and the number of port queues.
  • the node in the network that will send the service will determine whether to send the service according to the detection message sent by the target node. To the target node.
  • Step 602 Determine the resource reservation mode supported by the target node according to the probe message, and determine whether the extended mode is supported for resource reservation. If the extended mode is supported for resource reservation, step 603 is performed; if the extended mode is not supported for resource reservation, step 601 is performed to receive the detection message of the target node.
  • the resource reservation in the extended mode can support more types of priorities and the number of port queues. Then, when a node that supports the extended mode of resource reservation sends a service packet, it needs to determine the next step on the traffic path. Node, that is, whether the target node supports resource reservation in the extended mode, if the target node supports resource reservation in the extended mode, it will send a request message carrying the resource reservation request to the target node; if not, continue to accept other The detection message of the target node.
  • the detection message is also extended at the same time, so that the detection message can be used to determine whether the device of the target node supports resource reservation in an extended manner, avoiding modification of the standard procedure of the existing resource reservation protocol.
  • the fourth field in the detection message that is used to indicate the number of priority categories supported by the target node is first acquired. Then compare the length of the fourth field with the length of the second field in the request message. Since in the message, the maximum value that a field can represent is limited by the length of the field, it can be compared according to the field length The maximum number of priorities that can be represented in the probe message and the number of priority categories in the second field.
  • 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.
  • the length of the field recording the number of supported priorities in the probe message is extended, so that the length of the field carrying the number of priorities in the probe message is the same as the length of the field carrying the extended priority in the request message.
  • the existing protocol process can be used to Detect the resource reservation method supported by the row node.
  • the structure of the Domain Discovery message in the prior art is shown in Fig. 7, and the structure of the Domain Discovery message after expansion is shown in Fig. 8 shown.
  • the length of the SRClassID and SRClassPriority fields are both 8 bits, which means that a maximum of 256 priority levels can be expressed in the Domain Discovery message.
  • the lengths of the SRClassID and SRClassPriority fields in the extended Domain Discovery message are both extended to 16 bits.
  • the fourth embodiment of the present invention relates to an electronic device. As shown in FIG. 9, it includes at least one processor 901 and at least one memory 902, where the memory 902 stores instructions that can be executed by at least one processor 901, and the instructions are at least One processor 901 executes, so that at least one processor 901 can execute the port resource reservation method in the first, second, or third embodiment.
  • the memory 902 and the processor 901 are connected in a bus manner.
  • the bus may include any number of interconnected buses and bridges, and the bus connects one or more various circuits of the processor 901 and the memory 902 together.
  • the bus can also connect various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all well-known in the art, and therefore, no further description will be given herein.
  • the bus interface provides an interface between the bus and the transceiver.
  • the transceiver may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on the transmission medium.
  • the data processed by the processor 901 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 901.
  • 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 may be used to store data used by the processor 901 when performing operations.
  • the fifth embodiment of the present invention relates to a computer-readable storage medium storing a computer program.
  • the computer program is executed by the processor, the above method embodiment is realized.
  • the program is stored in a storage medium and includes several instructions to enable a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

一种端口资源预留方法、电子设备及存储介质。本发明的方法包括：接收用于为业务预留资源的请求报文，并根据请求报文确定资源预留方式(S101)；当确定出资源预留方式为扩展方式时，根据预设的第一映射关系，获取请求报文中携带的扩展优先级对应的出端口队列(S103)，并在扩展优先级对应的出端口队列上为业务预留资源(S104)，其中第一映射关系是指扩展优先级与出端口队列的对应关系；从请求报文中获取业务标识，并建立第二映射关系(S105)，其中第二映射关系是指业务标识与扩展优先级的映射关系。

Description

端口资源预留方法、电子设备及存储介质
相关申请的交叉引用
本申请基于申请号为202010286428.2、申请日为2020年4月13日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及通信技术领域，特别涉及一种端口资源预留的方法、电子设备及存储介质。
背景技术
目前在通信技术领域，互联网用户对于以太网上的多媒体应用的需求日益剧增，因此各种用于互联网中质量整合服务的协议层出不穷。其中由IEEE提出的IEEE 802.1Qat标准中，提供了一种网络的流预留协议SRP(Stream Reservation Protocol)，SRP协议是一种分布式的资源预留协议，用于为时间敏感网络(Time Sensitive Network，TSN)业务流量建立转发表和预留带宽资源。SRP协议中的Talker Advertise报文中携带了长度为3bit的数据结构优先级字段(Data Frame Priority)，在协议运行过程中，通过IEEE802.1Qav中提出的优先级到traffic class的映射关系找到对应的预留资源的出端口队列。
然而，本申请的发明人发现，现有技术中，往往出现以下情况：SRP协议基于优先级字段进行出端口队列的资源预留，现有的长度为3bit的优先级字段仅支持最多7个类别，也就是说最多支持在7个出端口队列上进行资源预留，而实际的TSN业务类别远远大于7个类别，当网桥设备支持的出端口队列数目大于8个时，基于目前的SRP协议无法充分利用网桥设备支持的出端口队列资源来满足TSN业务的实际需求。
发明内容
本发明实施例的目的在于提供一种端口资源预留方法、电子设备及存储介质，可以为业务提供细粒度的资源分配服务。
为至少在一定程度上解决现有技术中的技术问题之一，本发明的实施例提供了一种端口资源预留方法，包括：接收用于为业务预留资源的请求报文，并根据请求报文确定资源预留方式；当确定出资源预留方式为扩展方式时，根据预设的第一映射关系，获取请求报文中携带的扩展优先级对应的出端口队列，并在扩展优先级对应的出端口队列上为业务预留资源；其中，第一映射关系是指扩展优先级与出端口队列的对应关系；从请求报文中获取业务标识，并建立第二映射关系；其中，第二映射关系是指业务标识与扩展优先级的映 射关系。
本发明的实施例还提供了一种电子设备，包括：至少一个处理器；以及，至少一个存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行如上述的端口资源预留方法。
本发明的实施例还提供了一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时实现如上述的端口资源预留方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，在附图中：
图1是根据本发明第一实施例中端口资源预留方法的流程图；
图2是根据本发明第一实施例中当前SRP协议中TalkerAdvertise报文的结构示意图；
图3是根据本发明第一实施例中扩展SRP协议中TalkerAdvertise报文的结构示意图；
图4是根据本发明第一实施例中网络设备建立X元组与IPV之间映射关系的示意图；
图5是根据本发明第二实施例中端口资源预留方法的流程图；
图6是根据本发明第三实施例中端口资源预留方法的流程图；
图7是根据本发明第三实施例中当前SRP协议中Domain Discovery报文的结构示意图；
图8是根据本发明第四实施例中扩展SRP协议中Domain Discovery报文的结构示意图；以及
图9是根据本发明第五实施例中电子设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及各实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。本发明的第一实施例涉及一种端口资源预留的方法，应用于网桥设备，在本实施例中，接收用于为业务预留资源的请求报文，并根据请求报文确定资源预留方式；当确定出资源预留方式为扩展方式时，根据预设的第一映射关系，获取请求报文中携带的扩展优先级对应的出端口队列，并在扩展优先级对应的出端口队列 上为业务预留资源；其中，第一映射关系是指扩展优先级与出端口队列的对应关系；从请求报文中获取业务标识，并建立第二映射关系；其中，第二映射关系是指业务标识与扩展优先级的映射关系。
本发明实施例当接收到为业务预留资源的请求报文时，若根据请求报文确定出当前使用扩展方式进行资源预留，则根据预设的映射关系来找到请求报文中携带的扩展优先级所对应的出端口队列；然后从请求报文中获取业务的业务标识，建立业务标识与扩展优先级之间的映射关系。即，本实施例中在资源预留时提出了一种扩展方式，预设扩展优先级与出端口队列的第一映射关系，并根据请求报文中业务标识和扩展优先级，为业务建立业务标识与扩展优先级的第二映射关系；通过该第一映射关系、第二映射关系，为该业务确定出业务标识、扩展优先级、出端口队列三者的映射关系；通过这种扩展方式，可以基于现有的报文传输协议上，扩展资源分配中所能支持的优先级数量，从而能够充分地利用到网络设备中的出端口队列资源，来为业务报文提供细粒度的端口资源预留服务。
下面结合附图，对本实施例作进一步阐述。
本实施例中的端口资源预留方法如图1所示，具体包括：
步骤101，接收用于为业务预留资源的请求报文，根据报文确定资源预留方式。
具体的说，本实施例中的端口资源预留方法是对现有资源预留协议的扩展。请求报文由业务发送端向业务传输路径的下一节点发送，用于通知下一节点为将要接收的业务预留出合适的带宽资源。请求报文中包含用于指示资源预留协议运行时资源预留方式的数据。其中，资源预留协议具有两种资源预留方式，包括：默认方式和扩展方式。上述传输路径中的下一节点在接收到请求报文后，根据请求报文中的数据来确定当前资源预留的方式。
在一个具体实现中，以SRP协议为例，请求报文为Talker Advertise报文，报文结构如图2所示。Talker Advertise报文中，通过DataFramePriority字段来承载默认优先级信息，该字段的长度为3bit(比特)，最多只能支持8种优先级。在协议运行过程中，由于需要预留一个优先级给BE(Best Effort)业务，因此实际只能支持在数量最多7个的出端口队列上进行资源预留。本实施方式中可以对现有承载优先级信息字段进行扩展，具体的手段包括但不限于在Talker Advertise报文中添加一个新的字段内部优先级(Internal Priority Value,IPV)，即上述的扩展优先级，其长度为N bit，其中，N为大于三的自然数，支持的优先级数量为2 n，对应所支持的出端口队列数量为2 n-1。
当网络设备接收到扩展的Talker Advertise报文时，可以根据IPV字段中的取值来判断当前所采用的资源预留方式。其中，若IPV字段的取值位在0～7的范围内，则IPV字段处于无效状态，此时仍采用默认的资源预留方式进行端口资源预留；若IPV字段的取值 大于7，则采用扩展方式进行端口资源预留。
在一个例子中，资源预留协议以SRP协议为例，请求报文为Talker Advertise报文，第三字段可以是Talker Advertise报文中的Reserved字段，Reserved字段在协议标准中为一段空白的字段，因此可以利用该字段来作为第三字段来保存指示业务标识的相关数据。此外，还可以在Talker Advertise报文中新添加一个Indicate字段作为第三字段来保存指示业务标识的相关数据。扩展后的Talker Advertise报文的结构如图3所示，其中新添加的报文内容位于IPVAndIndication这一行，包括长度为16bit的IPV字段以及长度为8bit的Indicate字段。
在一个具体实现中，还可以通过1bit的数据来作为资源预留方式的指示器，这1bit的数据可以占用1bit的长度保存在Talker Advertise报文的Reserved字段或是新添加的Indicate字段中。例如选用Reserved字段的第一个bit作为资源预留方式的指示器，若该bit的数据为0，则表示仍根据协议中所规定的默认方式进行资源预留，若该bit的数据为为1，则表示根据扩展方式进行资源预留。
在此实施例中，请求报文中预设有用于指示资源预留方式的第一字段和用于指示扩展优先级的第二字段。即，第一字段专门用于指示资源预留方式，第二字段专门用于扩展优先级；在请求报文中以新增字段的方式来携带资源预留方式的信息以及扩展优先级的信息，能够在不影响以现有的传输协议传输请求报文并进行资源预留的情况下，实现本申请中提出的以扩展方式进行资源预留；由于与现有的传输协议并不冲突，因此实现起来较为简便且比较灵活。
另外，请求报文为TalkerAdvertise报文，第三字段为Reserved字段。在SRP协议的应用场景下，在TalkerAdvertise报文中利用Reserved字段或者新添加的Indicate字段来承载指示资源预留方式的第一字段和用于指示扩展优先级的第二字段，减少对协议报文结构的修改，提高网桥设备对于扩展后协议的兼容性。
步骤102，判断是否采用扩展方式进行资源预留。
当根据业务报文确定出当前以默认方式进行资源预留时，资源预留的流程与目前资源预留协议的标准流程一致，执行步骤113至步骤114。
步骤113，根据请求所基于的传输协议，获取请求报文中携带的默认优先级对应的出端口队列。
具体地说，所述传输协议以SRP协议为例，请求报文中通过DataFramePriority字段来承载默认优先级信息，协议中建议的默认优先级与出端口队列的对应关系如下表所示：
Figure PCTCN2021070267-appb-000001
在实际应用中，除了可以根据上表中的对应关系来确定预留资源的出端口队列(Traffic Class)；此外，也可以预先由用户根据需求来设置个性化的默认优先级与出端口队列的对应关系。
步骤114，在默认优先级对应的出端口队列上为业务预留资源。
具体地说，所述传输协议以SRP协议为例，请求报文中通过DataFramePriority字段来承载默认优先级信息，根据DataFramePriority字段确定优先级后，根据预设的优先级与出端口队列的映射关系，在优先级对应的出端口上进行资源预留。
当根据业务报文确定当前以扩展方式进行资源预留时，执行步骤102。
步骤103，根据预设的第一映射关系，获取请求报文中携带的扩展优先级对应的出端口队列。
IPV TrafficClass
8 5
9 7
10 9
11 10
12 11
13 12
14 13
在实际的应用中，既可以根据当前的实际需求，比如网桥设备的端口数量来设置合适的字段长度，也可以设置一个较长的字段，以尽可能地兼容同一网络中不同端口数量的网 桥设备。假设当前所设定的IPV字段长度为8bit，则表示IPV的取值可以为0～256。在获取到Talk Advertise报文后，读取IPV字段的取值。由于扩展的IPV字段仍需要对默认优先级进行兼容，在优先级为0～7时采用默认方式进行资源预留。因此在前述已经确定采用扩展方式进行资源预留的前提下，如果读取到的IPV字段取值在0～7内，说明资源预留方式与优先级发生错误，则资源预留失败。
步骤104，在扩展优先级对应的出端口队列上为业务预留资源。
具体地说，在找到与扩展优先级对应的出端口队列后，根据请求报文中携带的业务特征计算需要的带宽资源并在该队列上预留带宽资源。
在一个具体实现中，以SRP协议为例，业务特征携带在Talker Advertise报文的TSpec(Traffic Specification)字段中，TSpec记载了业务的流量参数。
步骤105，从请求报文中获取业务标识，建立第二映射关系。
具体地说，第二映射关系是指业务标识与扩展优先级之间的映射关系。在现有技术中，通常直接采用业务报文中的优先级字段(如TSN报文中的PCP字段)来进行业务报文与优先级的匹配，因此在获取到业务报文后，能够直接确定对应出端口队列，从而将业务报文放入预留的出端口队列中。在本实施例中，由于扩展优先级所支持的优先级数量大于现有技术中的优先级字段能够记载的优先级数量，因此可以根据请求报文获取业务标识，业务标识可以包括优先级字段，也可以包括如虚拟局域网标识VLANID、目标地址IP等特定的业务信息，将这些业务信息进行组合可以区分出更多数量的业务类别，从而对业务种类进行细分，再提供细粒度的资源预留服务。
在业务标识与扩展优先级之间建立第二映射关系，目的是用于在接收到后续的业务报文时，根据业务报文中所携带的业务标识，在第二映射关系中查找该业务报文所对应的优先级信息，从而将业务报文放入预留的出端口队列中，完成业务调度过程。
进一步说，业务标识通过请求报文中携带的第三字段来确定。首先从请求报文中提取与业务标识关联的第三字段的取值，然后根据第三字段的取值和预设的第三映射关系，获取业务标识。其中，第三映射关系是指第三字段取值与业务表示的映射关系。通过以上手段，业务标识与第三字段取值的映射关系预先保存在网络设备本地进行维护，能够根据需要来提取不同的数据所组成的业务标识，灵活的对业务进行区分，提供更好的资源预留服务。其中，第三字段可以根据需要设置长度，即可以将第三字段设置得较短，并通过业务标识与第三字段的取值的映射关系来得到相对数据量较大的业务标识；从而能够缩短请求报文的报文长度，提高请求报文的处理效率以及节省请求报文的带宽开销。
在一个具体实现中，业务标识是由X个业务报文中的字段取值所组成的报文X元组， 其中X为大于1的自然数。通过第三字段和第三映射关系，来确定出业务报文中具体组成X元组的字段，每一个第三字段的取值与一种X元组的字段组成相对应。
在一个例子中，第三字段的取值和X元组的字段组成如下表所示：
第三字段取值X元组的字段组成
第三字段取值 X元组的字段组成
1 {SrcMac,PCP,DestMulticastMac,VlanID}
2 {DestMultiCastMac,VlanID,PCP}
3 {SrcMac,VlanID}
… …
假定当前采用Reserved字段(或Indicate字段)的2～4bit(共3bit)来保存指示业务标识的相关数据，则可以指示有8种决定X元组内容的方式。若值为0，可表示采用包头中3-tuple{SrcMac,destMulticastMac,VlanID}作为查找对应IPV时的TSN流量识别标志，值为1时可表示采用包头中X元组{SrcMac,PCP,DestMulticastMac,VlanID}作为TSN业务报文识别的标识，值为2时X元组为{DestMultiCastMac,VlanID,PCP}，值为3时X元组为{SrcMac,VlanID}等。
从Talker Advertise报文中确定X元组后，建立X元组与IPV之间的映射关系，具体映射方式如图4所示：
其中，节点1(Stream1Talker)为一号业务发送节点，经过节点3向节点4(Stream1Listener)发送TalkerAdvertise报文，报文中所携带的X元组为{01:00:5e:00:01:00,500,2}({目标地址Destination，虚拟局域网标识VLANID，内部数据优先级DataFramePriority})、IPV为10，然后节点4根据报文中的数据建立X元组-IPV的映射关系；节点2(Stream1Talker)为二号业务发送节点，报文中所携带的X元组为{01:00:5e:00:01:00,100}({Destination，VLANID})、IPV为11，经过节点3向节点5(Stream1Listener)发送TalkerAdvertise报文，然后节点4根据报文中的数据建立X元组-IPV的映射关系。其中，节点4与节点5所建立的第二映射关系已在图中表示；由于一号业务与二号业务均从节点3通过，因此节点3根据一号业务和二号业务的TalkerAdvertise报文所建立的第二映射关系如下表所示：
X元组 IPV
{01:00:5e:00:01:00,500,2} 10
{01:00:5e:00:01:01,100} 11
在实际应用中，上述节点4或节点5在根据TalkerAdvertise报文建立X元组-IPV的映射关系后，可以使用IEEE 802.1Qci组件来实现对映射表的维护，具体如下表所示：
Figure PCTCN2021070267-appb-000002
在FilterInstanceTable中通过SRP扩展协议配置两个FilterInstance表项，表项ID分别为1和2，FilterInstanceID 1对应的表项StreamHandle为{DestMulticastMac,VLANID,pcp}＝{01:00:5e:00:01:00,500,2}，FilterInstanceID 2对应的表项StreamHandle为{DestMulticastMac,VLANID}＝{01:00:5e:00:01:01,100}，两个FilterInstance表项对应的GateInstanceTable ID分别为1和2，SRP扩展协议在GateInstanceTable配置两个ID为1和2的表项，两个表项的门状态始终为“O”，IPV分别为10和11。上述配置表明，包头和FilterInstanceID为1的表项匹配的TSN数据包映射到IPV 10，而和FilterInstanceID为2表项匹配的数据包映射到IPV 11。
需要说明的是，本实施例中的上述各示例均为方便理解进行的举例说明，并不对本发明的技术方案构成限定。
本实施例中通过对现有的资源预留方式进行扩展，并同时保留原有的资源预留方式。当接收到为业务预留资源的请求报文时，若根据请求报文确定出当前使用扩展方式进行资源预留，则根据预设的映射关系来找到请求报文中携带的扩展优先级所对应的出端口队列；然后从请求报文中获取业务的业务标识，建立业务标识与扩展优先级之间的映射关系。优先级与出端口队列具有一一对应的关系，而扩展优先级支持的类别数量远高于现有技术中的优先级支持的类别数量，从而能够充分地利用到网桥设备中的端口资源来为业务报文提供细粒度的端口资源预留服务。
本发明的第二实施例涉及一种端口资源预留方法，下面结合附图对本实施例中进行详细阐述，本实施例中的端口资源预留方法如图5所示，包括：
步骤501，接收用于为业务预留资源的请求报文，根据请求报文确定资源预留方式。
该步骤与本发明第一实施例中的步骤101相同，相关的实施细节已在本发明第一实施例中详细说明，在此不再赘述。
步骤502，判断是否采用扩展方式进行资源预留，若采用扩展方式进行资源预留，则执行步骤513至步骤515。
具体地说，采用扩展方式进行资源预留的方法步骤流程为步骤513至步骤515。步骤513至步骤515与本发明第一实施例中的步骤102至步骤104相同，相关的实施细节已在本发明第一实施例中详细说明，在此不再赘述。
若采用默认方式进行资源预留，则执行步骤523至步骤524。
步骤523，根据请求所基于的传输协议，获取请求报文中携带的默认优先级对应的出端口队列。
步骤524，在默认优先级对应的出端口队列上为业务预留资源。
步骤516，接收业务报文，并在第二映射关系中查找业务报文中携带的业务标识。
步骤517，判断是否查找到业务报文中携带的业务标识；若查找到业务报文中携带的业务标识，则表示该业务是根据扩展方式进行的资源预留，那么执行步骤518至步骤519；；若未查找到业务报文中携带的业务标识，则表示该业务是根据默认方式进行的资源预留，那么执行步骤525至步骤526。
步骤518，根据第二映射关系以及第一映射关系，获取第一目标队列。
步骤519，将业务报文放入第一目标对列，并基于将目标队列处预留的资源发送业务报文。
具体地说，现有的资源预留协议中，业务在网路中传输时，由一个节点转发至下一个节点时，首先会由发送节点向业务转发路径上的下一个节点发送请求报文，用来指示下一节点为该业务在端口上预留带宽资源。在本实施例中，在业务报文达到节点时，已经进行过预留资源的节点会提取业务报文中的业务标识，然后在第二映射关系查找该业务标识，若第二映射关系中存在该业务标识，则表示业务预先以扩展方式进行资源预留，根据业务标识与扩展优先级之间的第二映射关系确定该业务的扩展优先级，然后再根据预设的第一映射关系确定出扩展优先级所对应的出端口队列，将业务报文放入该出端口队列，以预先预留的带宽资源进行转发。本实施例提供了基于扩展方式在出端口队列预留资源后，为接收到的业务报文找到对应的出端口队列的一种方式；即，业务报文中预设业务标识，从而可以根据第一映射关系以及第二映射关系确定出业务报文的出端口队列。由于优先级数量更多，能够对应更多的出端口队列，提高端口资源的利用效率。
在一个具体实现中，业务报文以TSN报文为例，业务标识为本发明第一实施例中提到 的在步骤104中所提取的X元组，TSN报文中同样携带了X元组中的多个字段，这些字段位于报文的开始部分，也就是包头字段。因此网络设备在接收到TSN报文后，首先会在第二映射关系也就是X元组与IPV优先级的第二映射关系中查找是否存在TSN报文中所携带的包头字段取值。如果存在TSN报文中所携带的包头字段取值，则根据第二映射关系确定X元组对应的IPV优先级，然后进一步根据IPV优先级与出端口队列的映射关系确定预留资源的出端口队列，将TSN业务报文放入该出端口队列进行发送。
步骤525，根据业务报文获取第二目标队列。
步骤526，将业务报文放入第二目标队列，并基于将第二目标队列处预留的资源发送业务报文。
具体地说，若未查找到业务报文中携带的业务标识，则表示该业务是根据默认方式进行的资源预留，那么则直接根据业务报文中承载优先级信息的字段来确定与优先级字段所对应的出端口队列。
在一个例子中，假设当前的TSN网络环境中存在9条业务流量，如下表所示：
StreamID 流量类型 Class_Measure_Interval 时延上界要求
1 ISOchronous-Cyclic real-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
且各网络设备上均运行SRP协议。其中每一条业务流量均具有不同的流量类型、class_measure_interval、时延上界要求。第1～8条业务流量为确定性业务流量，需要SRP协议为其分配带宽资源，这八种流量对网络的服务质量和服务等级要求不同。
若采用当前的SRP协议，这八种流量会被分配在同一个SR Class和优先级提供服务，而当前SRP协议仅支持最多7种SR Class类别，表示最少有两条业务流需要强制划分在同一个优先级提供服务，例如第7和第8条流量的内部数据优先级DataFramePriority均为7具体如下表所示：
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
若采用本实施例中所提出的扩展的SRP协议，在接收到业务流量的TalkerAdvertise报文后，各网络节点网络设备根据报文的中添加的IPV字段进行资源预留，则能够为每条有不同网络服务要求的业务分配各自的SR Class和内部优先级IPV，从而提供更加细粒度的服务，具体如下表所示：
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
其中，StreamID为业务编号，SR ClassID为优先级标识，IPV为扩展优先级，TrafficClass为对应进行资源预留的出端口队列号。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本实施例使得扩展后的资源预留方式仍然能够兼容现有技术中默认的资源预留方式，能够在接收到携带有默认优先级的请求报文时仍提供正常的端口资源预留服务。网络设备在接收到业务报文时，先根据业务报文中的业务标识查找出端口队列，当基于业务报文中的业务标识查找出端口队列时，根据默认优先级所对应的出端口队列进行发送；本实施例提供了为业务报文查找已经预留资源的出端口队列的一种方式，以默认方式或以扩展方式进行资源预留的业务报文，均能够在本设备进行发送。
本发明的第三实施例涉及一种端口资源预留方法，该实施例与本发明的第二实施例大致相同，区别之处在于：在本实施例中除了对请求报文的结构以及业务资源预留的方式进行扩展，同时还对进行资源预留的前提，即网络域边界探测中的探测报文进行了扩展，但该扩展并不对域边界探测的具体工作过程造成影响。
下面结合附图，对本实施例作进一步阐述。
本实施例中的域边界探测流程如图6所示，具体包括：
步骤601，接收目标节点的探测报文。
具体地说，目标节点所发送的探测报文中携带有目标节点所支持的优先级数量以及端口队列数量，网络中将要发送业务的节点会根据目标节点发送的探测报文来判断是否将业务发送至该目标节点。
步骤602，根据探测报文确定目标节点支持的资源预留方式，判断是否支持扩展方式进行资源预留。若支持扩展方式进行资源预留，而执行步骤603；若不支持扩展方式进行资源预留，则执行步骤601，接收目标节点的探测报文。
具体的说，以扩展方式来进行资源预留，可以支持更多种类的优先级以及端口队列数量，那么支持扩展方式预留资源的节点发送业务报文时，则需要判断流量路径上的下一节点，即目标节点是否支持扩展方式预留资源，如果目标节点支持以扩展方式进行资源预留，则向该目标节点发送携带有资源预留请求的请求报文；若不支持，则继续接受其他目标节点的探测报文。通过上述手段，同时对探测报文也进行扩展，使得能够通过探测报文判断目标节点的设备是否支持以扩展方式进行资源预留，避免对现有资源预留协议的标准流程进行修改。
进一步讲，当获取到来自目标节点的探测报文时，首先获取探测报文中用于指示目标节点所支持的优先级类别数量的第四字段。然后比较第四字段的长度与请求报文中第二字段的长度，由于在报文中，一个字段所能表示的最大数值受限于该字段的所占用的长度，因此可以根据字段长度来比较探测报文中最多能够表示的优先级数量和第二字段中优先级的类别数量。也就是说，若第四字段的长度大于或等于第二字段的长度，则确定目标节 点支持以扩展方式进行资源预留；若第四字段的长度小于第二字段的长度，则确定目标节点不支持以扩展方式进行资源预留。对探测报文中记载支持优先级数量的字段进行长度扩展，使探测报文中承载优先级数量的字段长度与请求报文中承载扩展优先级的字段长度一致，能够采用现有的协议流程来探测行节点所支持的资源预留方式。
在一个具体实现中，以SRP协议中的进行域边界探测的Domain Discovery报文为例，现有技术中的Domain Discovery报文的结构如图7所示，扩展后Domain Discovery报文的结构如图8所示。扩展前的Domain Discovery报文中，SRClassID以及SRClassPriority字段的长度均为8bit，表示Domain Discovery报文中最多能够表示256种优先级数量。为了与本发明第一实施例中提到的IPV字段的长度相匹配，与IPV字段能够支持的优先级数量相同，扩展后的Domain Discovery报文中SRClassID以及SRClassPriority字段的长度均扩展为16bit。
第一实施例和第二实施例中提到的相关技术细节在本实施方式中依然有效，在第二实施例中所能达到的技术效果在本实施例中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施例中提到的相关技术细节也可应用在第一实施方式和第二实施方式中。
本发明第四实施例涉及一种电子设备，如图9所示，包括至少一个处理器901以及至少一个存储器902，其中，存储器902存储有可被至少一个处理器901执行的指令，指令被至少一个处理器901执行，以使至少一个处理器901能够执行第一、第二、或第三实施例中的端口资源预留方法。
其中，存储器902和处理器901采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器901和存储器902的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器901处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器901。
处理器901负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器902可以被用于存储处理器901在执行操作时所使用的数据。
本发明第五实施例涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述方法实施例中的全部或部分步骤是可以通过 程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述是实现本发明的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本发明的精神和范围。

Claims (10)

  1. 一种端口资源预留方法，包括：
    接收用于为业务预留资源的请求报文，并根据所述请求报文确定资源预留方式；
    当确定出资源预留方式为扩展方式时，根据预设的第一映射关系，获取所述请求报文中携带的扩展优先级对应的出端口队列，并在所述扩展优先级对应的出端口队列上为所述业务预留资源，其中所述第一映射关系是指扩展优先级与出端口队列的映射关系；以及
    从所述请求报文中获取业务标识，并建立第二映射关系，其中所述第二映射关系是指所述业务标识与所述扩展优先级的映射关系。
  2. 根据权利要求1所述的端口资源预留方法，其中，在所述从所述请求报文中获取业务标识，并建立第二映射关系之后，还包括：
    接收业务报文，并在所述第二映射关系中查找所述业务报文中携带的业务标识；
    当在所述第二映射关系中查找到所述业务报文中携带的业务标识时，根据所述第二映射关系以及所述第一映射关系，获取第一目标队列，其中所述第一目标队列是指所述业务报文中携带的业务标识对应的出端口队列；以及
    将所述业务报文放入所述第一目标队列，并基于将所述第一目标队列处预留的资源发送所述业务报文。
  3. 根据权利要求2所述的端口资源预留方法，其中，在所述根据请求报文确定预留资源的方式之后，还包括：
    当确定出资源预留方式为默认方式时，根据所述请求报文所基于的传输协议，获取所述请求报文中携带的默认优先级对应的出端口队列，并在所述默认优先级对应的出端口队列上为所述业务预留资源；以及
    其中，所述在所述第二映射关系中查找所述业务报文中携带的业务标识之后，还包括：
    当在所述第二映射关系中未查找到所述业务报文中携带的业务标识时，根据所述请求报文所基于的传输协议，获取第二目标队列，其中所述第二目标队列是指所述业务报文中携带的默认优先级对应的出端口队列；
    将所述业务报文放入所述第二目标队列，并基于将所述第二目标队列处预留的资源发送所述业务报文；所述第二目标队列为所述第二目标队列。
  4. 根据权利要求1所述的端口资源预留方法，其中，所述请求报文中预设有用于指示所述资源预留方式的第一字段和用于指示所述扩展优先级的第二字段。
  5. 根据权利要求1所述的端口资源预留方法，其中，所述从所述请求报文中获取业务标识，包括：
    从所述请求报文中提取与业务标识关联的第三字段的取值；以及
    根据所述第三字段的取值和预设的第三映射关系，获取所述业务标识，其中所述第三映射关系是指第三字段的取值与业务标识的映射关系。
  6. 根据权利要求5所述的端口资源预留方法，其中，所述请求报文为流预留协议SRP中的TalkerAdvertise报文，所述第三字段为Reserved字段。
  7. 根据权利要求2所述的端口资源预留方法，其中，在所述将所述业务报文放入所述第一目标队列，并基于将所述第一目标队列处预留的资源发送所述业务报文之前，还包括：
    接收目标节点的探测报文，且根据所述探测报文确定所述目标节点支持的资源预留方式；
    若所述目标节点支持的资源预留方式包括所述扩展方式，向所述目标节点发送所述请求报文；以及
    所述将所述业务报文放入所述第一目标队列，并基于将所述第一目标队列处预留的资源发送所述业务报文，其中，将所述业务报文放入所述第一目标队列，并基于将所述第一目标队列处预留的资源向所述目标节点发送所述业务报文。
  8. 根据权利要求7所述的端口资源预留方法，其中，所述根据所述探测报文确定所述目标节点支持的资源预留方式，包括：
    根据所述探测报文中的第四字段的长度确定所述目标节点支持的资源预留方式；其中，所述第四字段为用于指示所述目标节点所支持的优先级数量的字段，或者，所述第四字段为用于指示所述目标节点所支持的业务类别的字段；其中，所述业务类别和所述优先级的数量相同且一一对应。
  9. 一种网络设备，其特征在于，包括：
    至少一个处理器；以及，
    至少一个存储器；
    其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至8中任一项所述的端口资源预留方法。
  10. 一种计算机可读存储介质，存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1至8中任一项所述的端口资源预留方法。
PCT/CN2021/070267 2020-04-13 2021-01-05 端口资源预留方法、电子设备及存储介质 Ceased WO2021208529A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
ES21788443T ES3018109T3 (en) 2020-04-13 2021-01-05 Port resource reservation method, electronic device, and storage medium
EP21788443.6A EP4087315B1 (en) 2020-04-13 2021-01-05 Port resource reservation method, electronic device, and storage medium
US17/759,888 US12273276B2 (en) 2020-04-13 2021-01-05 Port resource reservation method, electronic device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010286428.2 2020-04-13
CN202010286428.2A CN113543234B (zh) 2020-04-13 2020-04-13 端口资源预留方法、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2021208529A1 true WO2021208529A1 (zh) 2021-10-21

Family

ID=78084150

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070267 Ceased WO2021208529A1 (zh) 2020-04-13 2021-01-05 端口资源预留方法、电子设备及存储介质

Country Status (5)

Country Link
US (1) US12273276B2 (zh)
EP (1) EP4087315B1 (zh)
CN (1) CN113543234B (zh)
ES (1) ES3018109T3 (zh)
WO (1) WO2021208529A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852554A (zh) * 2021-11-29 2021-12-28 中国星网网络系统研究院有限公司 一种数据传输方法、装置及设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116208555B (zh) * 2021-12-01 2024-08-20 南京盛科通信有限公司 数据调度方法、装置及计算机可读存储介质
CN114531721A (zh) * 2022-01-28 2022-05-24 新华三技术有限公司 一种建立隧道、报文的处理的方法和ac
CN118802530B (zh) * 2024-09-12 2024-12-24 杭州海康威视数字技术股份有限公司 网络更新方法和电子设备
CN120880980A (zh) * 2025-09-25 2025-10-31 中移(苏州)软件技术有限公司 一种流表生成方法、装置、设备、存储介质及产品

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105191234A (zh) * 2013-03-29 2015-12-23 三菱电机株式会社 在网状通信网络中分配资源的方法、计算机程序、信息存储装置和节点设备
US20160036926A1 (en) * 2014-07-29 2016-02-04 Harman International Industries, Incorporated Resource management for stream reservations
CN108270674A (zh) * 2016-12-30 2018-07-10 华为技术有限公司 一种报文转发的方法、装置
US20190238441A1 (en) * 2018-01-31 2019-08-01 Franz-Josef Götz Method for data communication in a network
CN110800224A (zh) * 2017-01-09 2020-02-14 高通股份有限公司 针对基于互易性的ul mimo传输的空中校准
WO2020035133A1 (en) * 2018-08-14 2020-02-20 Nokia Solutions And Networks Oy Mutual 3gpp-tsn qos adaption and shaping
CN110870285A (zh) * 2017-07-06 2020-03-06 西门子股份公司 在具有部分实时需求的数据网络中高性能数据传输的方法和执行该方法的装置

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100505685C (zh) * 2005-08-09 2009-06-24 华为技术有限公司 通信网络中对网络地址/端口转换请求进行处理的方法
US8060615B2 (en) * 2007-08-15 2011-11-15 Cisco Technology, Inc. Stream reservation protocol for bridged networks
CN101730236B (zh) * 2008-10-30 2015-05-20 中兴通讯股份有限公司 资源调度方法和系统、基站、以及终端
CN101841456B (zh) * 2009-03-18 2012-07-25 中国电信股份有限公司 一种实现业务应用区分的方法和系统
CN102104528B (zh) * 2009-12-21 2012-10-10 中国移动通信集团山西有限公司 一种应用于农村地区的网络系统及业务报文的传送方法
CN103597778A (zh) * 2011-06-08 2014-02-19 三星电子株式会社 用于音频视频网络的增强流预留协议
US8516130B2 (en) * 2011-06-30 2013-08-20 Harman International Industries, Incorporated Using non-AVB application layer interface and message to establish a connection over an AVB network
DE102012207952A1 (de) * 2012-05-11 2013-11-14 Continental Automotive Gmbh Verfahren zur Übertragung von Daten in einem paketorientierten Kommunikationsnetzwerk und entsprechend eingerichtetes Teilnehmergerät an dem Kommunikationsnetzwerk
EP2901640A2 (en) * 2012-09-26 2015-08-05 Interdigital Patent Holdings, Inc. Methods, systems and apparatuses for operation in long-term evolution (lte) systems
US9894124B2 (en) * 2013-07-16 2018-02-13 Harman International Industries, Incorporated Rapid startup with dynamic reservation capabilities for network communication systems
CN103780505A (zh) * 2014-01-27 2014-05-07 中国联合网络通信集团有限公司 业务处理方法和装置
CN104243628A (zh) * 2014-09-11 2014-12-24 杭州华三通信技术有限公司 一种连续多端口申请方法和装置
CN104468401B (zh) * 2014-11-20 2017-11-17 华为技术有限公司 一种报文处理方法和装置
WO2017146701A1 (en) * 2016-02-24 2017-08-31 Harman International Industries, Incorporated Data streaming with layer 2 and layer 3 reservations
US20230379385A1 (en) * 2016-03-21 2023-11-23 Transportation Ip Holdings, Llc Vehicle control system
JP2017204857A (ja) * 2016-05-12 2017-11-16 現代自動車株式会社Ｈｙｕｎｄａｉ Ｍｏｔｏｒ Ｃｏｍｐａｎｙ ネットワークにおいてストリームの通信経路設定方法
ES2987476T3 (es) * 2016-07-19 2024-11-15 Schneider Electric Ind Sas Redes definidas por software sensibles al tiempo
KR102164032B1 (ko) * 2016-12-19 2020-10-12 엘지전자 주식회사 네트워크 장치 및 네트워크 장치의 전송 선택 방법
EP3791622A1 (en) * 2018-05-08 2021-03-17 Nokia Solutions and Networks Oy Management & orchestration aided transparent of 3gpp network into tsn bases industrial network
CN108933739A (zh) * 2018-06-13 2018-12-04 烽火通信科技股份有限公司 一种端到端业务质量保障实现方法及系统
CN110278152B (zh) * 2018-08-31 2020-05-29 新华三信息安全技术有限公司 一种建立快速转发表的方法及装置
CN110891026B (zh) * 2018-09-07 2022-11-25 华为技术有限公司 一种流量调度方法、设备及系统
EP3629548B1 (de) * 2018-09-25 2021-07-07 Siemens Aktiengesellschaft Verfahren zur datenübermittlung innerhalb eines industriellen kommunikationsnetzes und kommunikationsgerät
US12177715B2 (en) * 2018-09-27 2024-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Methods for interworking between wireless and wired communication networks
CN109246023A (zh) * 2018-11-16 2019-01-18 锐捷网络股份有限公司 流量控制方法、网络设备及存储介质
US11356358B2 (en) * 2019-01-23 2022-06-07 Siemens Aktiengesellschaft Network node, computer program, computer-readable medium and method for fail-safe data transmission
EP3715983B1 (de) * 2019-03-28 2022-06-29 Siemens Aktiengesellschaft Verfahren zur bereitstellung von steuerungsanwendungen über ein kommunikationsnetz zur übermittlung zeitkritischer daten und koordinierungseinrichtung
US11159445B1 (en) * 2019-11-26 2021-10-26 Xilinx, Inc. Systems and methods for extending internal endpoints of a network device
EP3873009B1 (de) * 2020-02-28 2024-08-21 Siemens Aktiengesellschaft Verfahren zur synchronisation von steuerungsanwendungen über ein kommunikationsnetz zur übermittlung zeitkritischer daten, netzinfrastrukturgerät und kommunikationsendgerät

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105191234A (zh) * 2013-03-29 2015-12-23 三菱电机株式会社 在网状通信网络中分配资源的方法、计算机程序、信息存储装置和节点设备
US20160036926A1 (en) * 2014-07-29 2016-02-04 Harman International Industries, Incorporated Resource management for stream reservations
CN108270674A (zh) * 2016-12-30 2018-07-10 华为技术有限公司 一种报文转发的方法、装置
CN110800224A (zh) * 2017-01-09 2020-02-14 高通股份有限公司 针对基于互易性的ul mimo传输的空中校准
CN110870285A (zh) * 2017-07-06 2020-03-06 西门子股份公司 在具有部分实时需求的数据网络中高性能数据传输的方法和执行该方法的装置
US20190238441A1 (en) * 2018-01-31 2019-08-01 Franz-Josef Götz Method for data communication in a network
WO2020035133A1 (en) * 2018-08-14 2020-02-20 Nokia Solutions And Networks Oy Mutual 3gpp-tsn qos adaption and shaping

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LAN/MAN STANDARDS COMMITTEE OF THE IEEE COMPUTER SOCIETY: "Stream Reservation Protocol(SRP) Enhancements and Performance Improvements", IEEE STD 802.1QCC, 31 December 2018 (2018-12-31), pages 1 - 208, XP068132839 *
See also references of EP4087315A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852554A (zh) * 2021-11-29 2021-12-28 中国星网网络系统研究院有限公司 一种数据传输方法、装置及设备
CN113852554B (zh) * 2021-11-29 2022-03-04 中国星网网络系统研究院有限公司 一种数据传输方法、装置及设备

Also Published As

Publication number Publication date
ES3018109T3 (en) 2025-05-14
CN113543234B (zh) 2025-08-12
CN113543234A (zh) 2021-10-22
US20230083406A1 (en) 2023-03-16
EP4087315A4 (en) 2023-01-25
EP4087315A1 (en) 2022-11-09
EP4087315B1 (en) 2025-03-19
US12273276B2 (en) 2025-04-08

Similar Documents

Publication Publication Date Title
CN113543234B (zh) 端口资源预留方法、电子设备及存储介质
US7653047B2 (en) Guaranteeing quality of service (QoS) using bandwidth reservation in switch
US12255771B2 (en) Packet processing method and device, advertisement method and device, bridge node, source apparatus, storage medium, and packet processing system
EP3468123B1 (en) Method and device for use in processing low-latency traffic
WO2021180073A1 (zh) 报文传输方法、装置、网络节点及存储介质
JP4663761B2 (ja) パケット中継装置
CN102577257B (zh) 一种实现虚拟局域网标识转换的方法及装置
US11171860B2 (en) Method for obtaining target transmission route, related device, and system
US9565112B2 (en) Load balancing in a link aggregation
US12212454B2 (en) Data transmission method and system in time-sensitive network
CN113079109B (zh) 一种数据报文处理方法、系统、智能终端及存储介质
CN102315970B (zh) 数据中心桥接参数配置方法、系统及网络设备
EP2466796A1 (en) User access method, system and access server, access device
US6782428B1 (en) Allocation of asymmetric priority to traffic flow in network switches
CN101729420B (zh) 一种数据处理方法及装置
RU2598293C1 (ru) Способ и устройство для передачи стандартных данных конфигурации усовершенствованной системы выбора протокола передачи
WO2024051367A1 (zh) 分组报文传输方法、网络设备及可读存储介质
US8305918B2 (en) Method of configuring the quality-of-service profile of a given stream at an access node of a packet communications network
US9215088B2 (en) Identification of application sessions
WO2023051049A1 (zh) 网络架构、网络通信方法、电子设备及存储介质
US20060230146A1 (en) Method for generating super frame by using sub-frame in residential ethernet system
WO2023175754A1 (ja) パケット転送装置、パケット転送方法およびプログラム
CN113542136A (zh) 一种接口属性调整方法及装置
CN116055396B (zh) 一种数据转发的方法、装置、路由设备及存储介质
CN118804186A (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: 21788443

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021788443

Country of ref document: EP

Effective date: 20220801

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 17759888

Country of ref document: US