WO2022183890A1 - 帧抢占方法、装置、设备和存储介质 - Google Patents
帧抢占方法、装置、设备和存储介质 Download PDFInfo
- Publication number
- WO2022183890A1 WO2022183890A1 PCT/CN2022/075739 CN2022075739W WO2022183890A1 WO 2022183890 A1 WO2022183890 A1 WO 2022183890A1 CN 2022075739 W CN2022075739 W CN 2022075739W WO 2022183890 A1 WO2022183890 A1 WO 2022183890A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- preemption
- emac
- frame
- sent
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000005540 biological transmission Effects 0.000 claims description 28
- 238000004891 communication Methods 0.000 claims description 17
- 230000015654 memory Effects 0.000 claims description 17
- 239000012634 fragment Substances 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 8
- 230000003068 static effect Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 12
- 230000007246 mechanism Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000001934 delay Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013467 fragmentation Methods 0.000 description 2
- 238000006062 fragmentation reaction Methods 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/245—Traffic characterised by specific attributes, e.g. priority or QoS using preemption
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
-
- 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/28—Flow control; Congestion control in relation to timing considerations
-
- 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/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
-
- 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/43—Assembling or disassembling of packets, e.g. segmentation and reassembly [SAR]
-
- 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/56—Queue scheduling implementing delay-aware scheduling
Definitions
- the present application relates to network communication technologies, and in particular, to a frame preemption method, apparatus, device, and storage medium.
- the IEEE 802.3br standard provides a frame preemption mechanism, and the new MMS (MAC Merge Sublayer, MAC merge sublayer) associates eMAC (express MAC, fast MAC) and pMAC (preemptable MAC, preemptible MAC) with a physical sublayer , as shown in FIG. 1 , the frame preemption of the eMAC to the pMAC can be realized. Due to the different transmission states of pMAC frames when frame preemption occurs, the existing frame preemption mechanism causes the preemption delay of each hop frame to be uncertain, resulting in frame preemption jitter related to the number of hops.
- MMS MAC Merge Sublayer, MAC merge sublayer
- An embodiment of the present application provides a frame preemption method, including: determining that a fast media access control eMAC message needs to be sent; and sending the eMAC message when the timing reaches a preemption delay target value.
- An embodiment of the present application provides a frame preemption device, comprising: an eMAC preemption determination module configured to determine that an eMAC message needs to be sent; an eMAC message transmission module configured to send the eMAC message when the timing reaches a preemption delay target value arts.
- An embodiment of the present application provides a communication device, including: a memory, and one or more processors; the memory is configured to store one or more programs; when the one or more programs are stored by the one or more programs The processor executes, causing the one or more processors to implement the method described in any of the above embodiments.
- An embodiment of the present application provides a storage medium, where a computer program is stored in the storage medium, and when the computer program is executed by a processor, the method described in any of the foregoing embodiments is implemented.
- FIG. 1 is a schematic diagram of a frame preemption mechanism component relationship and a preemption service primitive in the prior art
- FIG. 2 is a schematic flowchart of a frame preemption method provided by an embodiment of the present application
- FIG. 3 is a schematic diagram of the component relationship of a frame preemption mechanism provided by an embodiment of the present application.
- FIG. 4 is a schematic diagram of a frame preemption opportunity provided by an embodiment of the present application.
- FIG. 5 is a schematic diagram of a frame preemption opportunity provided by an embodiment of the present application.
- FIG. 6 is a schematic diagram of a frame preemption opportunity provided by an embodiment of the present application.
- FIG. 7 is a schematic diagram of a frame preemption opportunity provided by an embodiment of the present application.
- FIG. 8 is a schematic diagram of a preemption service primitive provided by an embodiment of the present application.
- FIG. 9 is a schematic flowchart of a frame preemption method provided by an embodiment of the present application.
- FIG. 10 is a schematic flowchart of a frame preemption method provided by an embodiment of the present application.
- FIG. 11 is a schematic structural diagram of a frame preemption apparatus provided by an embodiment of the present application.
- FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 2 is a schematic flowchart of a frame preemption method provided by an embodiment of the present application.
- the method is applicable to the case where the eMAC performs frame preemption on the pMAC, and the method can be executed by the frame preemption apparatus provided in this application, and the frame preemption apparatus can be implemented by software and/or hardware and integrated in the network communication equipment.
- the frame preemption method provided by this embodiment includes:
- the priority of eMAC packets is higher than that of pMAC packets.
- a high-priority eMAC packet can interrupt the sending of a low-priority pMAC packet to reduce the waiting time of a high-priority eMAC packet.
- determining that the eMAC message needs to be sent includes: if an eMAC message or a frame preemption request is received, determining that the eMAC message needs to be sent.
- the MMS component provides the MAC client (Client) component with a preemption service primitive MM_CTL.request, and the parameters of the MM_CTL.request can be preemption (HOLD) or release (RELEASE).
- HOLD preemption
- RELEASE release
- the MAC_Client component sends a frame preemption request to the MMS component, that is, a request in which the parameter of MM_CTL.request is HOLD, it can be determined that the eMAC needs to send data, that is, it is determined that the eMAC message needs to be sent.
- the MMS component receives the eMAC message, it can also determine that the eMAC needs to send data, that is, it is determined that the eMAC message needs to be sent.
- the frame preemption request may be sent to the MMS component through the MAC_Client component, or the frame preemption may be triggered by the eMAC message itself.
- the preemption delay target value is a determined value of the preemption delay of each frame.
- the preemption delay target value when the preemption delay target value is not counted, continue to determine whether to time the preemption delay target value until the eMAC message is sent when it is determined that the preemption delay target value is reached.
- a timer can be added to the MMS.
- the timer can be used to measure the elapsed time from receiving an eMAC packet or from receiving a frame preemption indication to allowing eMAC packet transmission.
- the timing parameter dpDelay of the timer is used to store the target value of the preemption delay, and the timing parameter dpDelay is configurable.
- the MMS can control the timer to start timing, and can also control the timer to reset (for example, clear), and the timer can report the timing status to the MMS.
- the preemption delay target value may be determined in at least one of the following manners:
- the MMS After frame preemption is triggered, the MMS stops sending pMAC packets within a specified time. When the pMAC packets stop sending, the MMS can start transmitting eMAC packets, thereby realizing frame preemption of pMAC by eMAC.
- the MMS When frame preemption occurs, in order to fully utilize the bandwidth, the MMS will fragment and transmit pMAC packets. If there is no pMAC message or the last bit of the pMAC message has just been transmitted, the fragmentation of the pMAC message is not involved; if the pMAC message is being sent, the total length of the frame, the number of transmitted bytes and the remaining The number of bytes is used to determine whether the pMAC packet can be fragmented, and to determine when the pMAC packet can give up the transmission opportunity.
- the minimum size of the non-last fragment is 64*(1+addFragSize)-4
- addFragSize is a parameter related to pMAC packet fragmentation in the IEEE 802.3br standard.
- the frame length of the pMAC packet is less than 64*(1+addFragSize)-4+64 bytes, the pMAC packet cannot be fragmented and cannot be preempted.
- the minimum value of the non-last fragment of the pMAC packet is 60 bytes, as shown in Figure 4, if the total frame length of the pMAC packet is less than 124 bytes, it cannot be preempted, only The transmission opportunity will not be given to eMAC until the frame transmission is completed; as shown in Figure 5, if the current frame has been transmitted ⁇ 60 bytes and the total frame length is ⁇ 124 bytes, when the frame is transmitted to 60 bytes, it can be preempted; As shown in Figure 6, if the frame has been transmitted ⁇ 60 bytes and the remaining frame length is ⁇ 64 bytes, it will be preempted immediately; as shown in Figure 7, if the frame has been transmitted ⁇ 60 bytes but the remaining frame length ⁇ 64 bytes , the transmission opportunity can only be given up after the entire frame transmission is completed.
- the preemption delay per hop frame is uncertain, resulting in a hop count related Preempt jitter. Therefore, in this embodiment, the frame preemption delay of each hop is set to a certain value, that is, the target value of the preemption delay is set to be stored in the timing parameter dpDelay of the timer, so as to eliminate the problem of frame preemption due to existing frame preemption. The jitter problem caused by the mechanism.
- the preemption delay target value may be calculated according to the minimum value of the non-last fragment of the media access control pMAC message that can be preempted and the port transmission rate when the communication device is started, and the calculated preemption delay target The value is stored in the timer's timing parameter dpDelay.
- the preemption delay target value may be set to be greater than or equal to the transmission duration of the largest fragment of the pMAC message.
- the minimum value of the non-last fragment of the pMAC message is 64*(1+addFragSize)-4 bytes.
- the maximum fragment length of a pMAC message is 64*(1+addFragSize)-4+64 bytes, that is, 64*(1+addFragSize)+59 bytes.
- the preemption delay target value is set to be greater than or equal to 64*(1+addFragSize)+59 bytes of transmission time, that is:
- M is the port speed
- the unit is bit/s.
- the MMS may calculate the preemption delay target value according to the above method, and store it in the timer dpDelay parameter.
- the preemption delay is determined as:
- the preemption delay is determined as:
- the preemption delay target value may also be obtained by external configuration.
- the preemption delay target value may be statically configured, which is suitable for the preemption delay configuration under the traffic determined in a specific scenario.
- the preemption delay target value may be configured on the network side, for example, the configuration is dynamically delivered through the southbound interface of the controller.
- the configuration parameters can be delivered to the timer in the MMS by the control plane via southbound interface protocols such as NETCONF (Network Configuration Protocol, network configuration protocol) and PCEP (Path Computation Element Protocol, path calculation protocol).
- This example is suitable for preemption delay configuration in flexible scenarios. For example, if the TSN service only requires real-time performance and has a high tolerance for jitter, the preemption delay target value can be set to 0. When there are strict requirements, an appropriate preemption delay target value can be delivered according to the specific requirements of the business.
- the preemption delay target value may also be configured according to a parameter carried in the frame preemption request. If the preemption command is triggered by the MAC_Client sending the preemption service primitive MM_CTL.request to the MMS, the dpDelay parameter can also be configured in the MAC_Client component, and then the dpDelay parameter can be carried to the MMS through the preemption service primitive.
- the eMAC message when frame preemption needs to be performed, the eMAC message will be sent only when the timer reaches the preemption delay target value in the dpDelay parameter. If the pMAC message is currently being sent, the transmission of the pMAC message is interrupted. When the sent bytes of the pMac message are less than 60 bytes, or the remaining bytes are less than 64 bytes, the pMac message continues to be sent, and in other cases , immediately stop sending pMac messages.
- an eMAC message is sent when the timing reaches the preemption delay target value, thereby realizing that the frame preemption delay of each hop is the predetermined value of the preemption delay target value. , thereby eliminating the end-to-end jitter problem caused by the existing frame preemption mechanism.
- the method when the timing reaches the preemption delay target value, before sending the eMAC message, the method further includes:
- the jitter-free frame preemption enable parameter is a parameter added in the MMS, and the parameter value is used to indicate whether to adopt the frame preemption method provided by the embodiments of the present application to eliminate the jitter problem caused by the existing frame preemption mechanism. For example, if the jitter-free frame preemption enable parameter value is valid, if the parameter value is true, the frame preemption method provided by the application embodiment is used; if the jitter-free frame preemption enable parameter value is invalid, if the parameter value is false, the Frame preemption method in the prior art.
- the jitter-free frame preemption enable parameter value is valid. If it is valid, the eMAC message is sent when the timing reaches the preemption delay target value. If it is invalid, the current frame Preemption mechanism processing.
- the jitter-free frame preemption enable parameter value may be determined in at least one of the following manners:
- the jitter-free frame preemption enabling parameter value may be delivered through the control plane, may be statically configured, or may be configured as a default value.
- the jitter-free frame preemption enable parameter value may be derived and determined according to the preemption delay target value, and may be derived and determined according to the dpDelay parameter (that is, the preemption delay target value) carried in the frame preemption request. , or it can be determined by derivation according to the stored dpDelay parameter. For example, if the target value of the preemption delay is greater than 0, the value of the enable parameter value of the jitter-free frame preemption is enabled by default, for example, the value of the enable parameter of the jitter-free frame preemption is set to true.
- the jitter-free frame preemption enable parameter value may also be configured according to a parameter carried in the frame preemption request. If the preemption command is triggered by the MAC_Client sending the preemption service primitive MM_CTL.request to the MMS, you can also configure the jitter-free frame preemption enable parameter to the MAC_Client component, and then carry the jitter-free frame preemption enable parameter to the MMS through the preemption service primitive.
- the parameters can be configured to the MAC_Client component, and then the MAC_Client can carry the configuration parameters to the MMS through the preemption service primitive.
- the configuration parameters are delivered to the MAC_Client component, two parameters are added to MM_CTL.request, which are used to indicate whether to enable the frame preemption method in the embodiment of the present application and to determine the preemption delay target value, wherein the preemption service primitive
- MM_CTL.request Two parameters are added to MM_CTL.request, which are used to indicate whether to enable the frame preemption method in the embodiment of the present application and to determine the preemption delay target value, wherein the preemption service primitive
- the modification is as shown in Figure 8, and the parameters deJitterEnabled and dpDelay are added in MM_CTL.request.
- dpDelay only one parameter dpDelay can be added to MM_CTL.request.
- the method when the timing reaches the preemption delay target value, before sending the eMAC message, the method further includes: if the timing has not been started, starting the timing; if the timing has been started, judging whether the timing has reached the preemption time The delay target value; correspondingly, after the eMAC message is sent, the method further includes: timing reset.
- the MMS After the MMS receives the eMAC message or the preemption indication, if the timing is not currently started, it starts timing, and if the timing has been started, it determines whether the timing reaches the preemption delay target value. Only when the timing reaches the preemption delay target value, the operation of sending the eMAC packet will be performed. After the eMAC message is sent, the timer is reset, for example, the timer can be reset.
- the MMS determines whether the timer has started to count. If the timer has not started to count, it controls the timer to start counting. If the timer has started, it asks the timer for its count. Timing duration, the timer reports its timing duration to the MMS, so that the MMS can determine whether the timer has counted up to the preemption delay target value.
- the timer starts timing, when the timer reaches the preemption delay target value, it can also actively report to the MMS that the timer has timed to the preemption delay target value.
- the timing In the case where the timing has been started, it indicates that there are eMAC packets received before to be sent. At this time, the currently received eMAC packets can be buffered. When the timing reaches the preemption delay target value, the previously received eMAC packets are sent. The eMAC packet to be sent and the currently received eMAC packet buffered. In this case, these eMAC packets can be considered as packets in a small period. Even if the frame preemption delays are not strictly consistent, the problem of end-to-end jitter caused by different frame preemption delays will not be caused.
- the method further includes: when a message is currently being sent, determining a message type of the sent message; when the message type is pMAC, interrupting the transmission of the pMAC message.
- the MMS After the MMS receives the eMAC message or the preemption indication, it determines whether the current MMS is sending the message. If not, the MMS starts the timer and starts timing when the timer is not started, and when the timer reaches the preemption time The eMAC message is sent when the target value is delayed. If it is, the message type of the currently sent message is judged first.
- determining the message type of the sent message may include: determining the message type of the sent message according to the value of the message sending variable.
- the message sending variable may be an internal variable indicating whether the MMS is sending an eMAC message, or an internal variable indicating whether the MMS is sending a pMAC message.
- emacTransmitting Take the message sending variable as an example of the internal variable emacTransmitting that indicates whether the MMS is sending eMAC messages. If the MMS is currently sending messages, if the value of emacTransmitting is true, it means that the MMS is sending eMAC messages. If emacTransmitting If the value is not true (such as false), it means that the MMS is sending pMAC packets.
- the method further includes: setting a variable value for sending the message.
- the value of emacTransmitting is set to true; after the eMAC message is sent, the value of emacTransmitting is set to false.
- the message type of the message being sent is eMAC
- the currently received eMAC message is directly sent, and the eMAC message can be cached until the currently sent message is sent.
- directly send the cached eMAC message that is, the currently received eMAC message
- set the message sending variable value to the value indicating that the MMS is sending the eMAC message, such as setting the value of emacTransmitting to ture
- the message sending variable value is set to a value indicating that the MMS is not sending an eMAC message. For example, if the value of emacTransmitting is set to false, the timer is reset and cleared.
- the transmission of the currently sent pMAC message needs to be interrupted, where the sent bytes of the pMac message are less than 60 bytes, or When the remaining bytes are less than 64 bytes, continue to send, otherwise stop the sending of pMac messages, and at the same time judge whether the timer starts timing, if not, start timing, and reach the preemption delay target when the timer counts
- the value of the eMAC message is sent, the value of the message sending variable is set to a value indicating that the MMS is sending the eMAC message, such as setting the value of emacTransmitting to true, and when the eMAC message is sent, the message is sent.
- the value of the message transmission variable is set to a value indicating that the MMS is not sending an eMAC message. For example, if the value of emacTransmitting is set to false, the timer is reset and cleared.
- FIG. 9 shows a schematic flowchart of a frame preemption method.
- the frame preemption method includes:
- the MMS receives the eMAC frame or the frame preemption indication.
- the MMS determines whether the value of the jitter-free frame preemption enabling parameter deJitterEnabled is true, and if not, executes S230, and if so, executes S240.
- the MMS executes the existing frame preemption process.
- the MMS judges whether the current MMS is sending a message, and if so, executes S250, and if not, executes S270.
- the MMS determines whether the value of the message transmission variable eMacTransmitting is true, and if so, executes S290, and if not, executes S260 and S270.
- the MMS interrupts the pMAC transmission.
- the pMac frame when the sent bytes of the pMac frame are less than 60 bytes, or the remaining bytes are less than 64 bytes, the pMac frame continues to be sent until the fragment or the sending ends, and the pMac frame transmission is stopped in other cases.
- the MMS determines whether the timer reaches the preemption delay target value dpDelay, and if so, executes S290, and if not, executes S280.
- the MMS sends the eMAC frame, and sets the value of the message sending variable eMacTransmitting to true.
- the MMS receives the eMAC frame or the frame preemption indication.
- the MMS determines that the parameter deJitterEnabled is configured to be true.
- the parameter deJitterEnabled is true, indicating that the jitter-free frame preemption process provided by the embodiment of the present application is enabled.
- the MMS determines that the message is currently being sent, and determines that the pMAC frame is currently being transmitted according to the value of the parameter emacTransmitting being false.
- the MMS interrupts the transmission of the pMAC frame, and starts a timer at the same time.
- the MMS sends the pMAC frame to 60 bytes, it fragments and stops sending the pMAC frame.
- the MMS judges whether the timer reaches 984ns, if not, continues to time and executes S350, and if so, executes S360.
- the MMS transmits the eMAC frame, and the value of the parameter emacTransmitting is set to true.
- FIG. 11 is a schematic structural diagram of a frame preemption apparatus provided in an embodiment of the present application, and the apparatus may be implemented by software and/or hardware and integrated in a network communication device.
- the frame preemption apparatus includes: an eMAC preemption determination module 410 and an eMAC packet transmission module 420 . in,
- the eMAC preemption determination module 410 is configured to determine that the eMAC message needs to be sent
- the eMAC message sending module 420 is configured to send the eMAC message when the timing reaches the preemption delay target value.
- an eMAC message is sent when the timing reaches the preemption delay target value, thereby realizing the determination that the frame preemption delay of each hop is the preemption delay target value value, thereby eliminating the end-to-end jitter problem caused by the existing frame preemption mechanism.
- the eMAC preemption determination module 410 is configured to determine that an eMAC packet needs to be sent if an eMAC packet or a frame preemption request is received.
- the preemption delay target value is determined in at least one of the following ways:
- the frame preemption apparatus further includes: a jitter-free frame preemption enable confirmation module, configured to confirm the jitter-free frame preemption enable parameter value before sending the eMAC message when the timing reaches the preemption delay target value. efficient.
- the jitter-free frame preemption enable parameter value is determined in at least one of the following manners:
- the frame preemption device further includes: a timing module, configured to start timing if the timing is not started before sending the eMAC message when the timing reaches the preemption delay target value, and if the timing has been started, then It is judged whether the timing reaches the preemption delay target value; after the eMAC message is sent, the timing is reset.
- a timing module configured to start timing if the timing is not started before sending the eMAC message when the timing reaches the preemption delay target value, and if the timing has been started, then It is judged whether the timing reaches the preemption delay target value; after the eMAC message is sent, the timing is reset.
- the frame preemption device further includes: a frame preemption module, configured to determine the message type of the sent message when the message is currently being sent; when the message type is pMAC, interrupt the pMAC. transmission of messages.
- a frame preemption module configured to determine the message type of the sent message when the message is currently being sent; when the message type is pMAC, interrupt the pMAC. transmission of messages.
- the frame preemption module is configured to determine the message type of the sent message according to the value of the message sending variable
- the frame preemption device further includes: a message sending variable setting module, configured to set the message sending variable value after sending the eMAC message and after sending the eMAC message.
- the frame preemption apparatus further includes: a timing loop judgment module configured to continue to judge whether the timing reaches the preemption delay target value when the timing is not reached to the preemption delay target value.
- the frame preemption apparatus provided in this embodiment is configured to implement the frame preemption method provided by the embodiment of the present application.
- the implementation principle and technical effect of the frame preemption apparatus provided in this embodiment are similar, and details are not described herein again.
- FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- the device provided by this application includes: a processor 510 and a memory 520 .
- the number of processors 510 in the device may be one or more, and one processor 510 is taken as an example in FIG. 12 .
- the number of memories 520 in the device may be one or more, and one memory 520 is taken as an example in FIG. 12 .
- the processor 510 and the memory 520 of the device may be connected through a bus or in other ways, and the connection through a bus is taken as an example in FIG. 12 .
- the communication device may be a network communication device.
- the communication device further includes a communication module configured to communicate and interact with other communication devices.
- the memory 520 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the frame preemption method in any embodiment of the present application (for example, the eMAC in the frame preemption device). preemption determination module 410 and eMAC message sending module 420).
- the memory 520 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the device, and the like.
- memory 520 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, memory 520 may further include memory located remotely from processor 510, which may be connected to the device through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
- the communication device provided above can be configured to execute the frame preemption method provided by any of the above embodiments, and has corresponding functions and effects.
- Embodiments of the present application further provide a storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute a frame preemption method when executed by a computer processor, the method comprising: determining that a fast media access control eMAC message needs to be sent message; when the timing reaches the preemption delay target value, the eMAC message is sent.
- user equipment encompasses any suitable type of wireless user equipment such as a mobile telephone, portable data processing device, portable web browser or vehicle mounted mobile station.
- the various embodiments of the present application may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof.
- some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
- Embodiments of the present application may be implemented by the execution of computer program instructions by a data processor of a mobile device, eg in a processor entity, or by hardware, or by a combination of software and hardware.
- Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
- ISA Instruction Set Architecture
- the block diagrams of any logic flow in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
- Computer programs can be stored on memory.
- the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
- Computer-readable media may include non-transitory storage media.
- the data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general purpose computer, a special purpose computer, a microprocessor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC) ), programmable logic devices (Field-Programmable Gate Array, FGPA) and processors based on multi-core processor architecture.
- DSP Digital Signal Processing
- ASIC Application Specific Integrated Circuit
- FGPA programmable logic devices
- processors based on multi-core processor architecture.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (12)
- 一种帧抢占方法,包括:确定需要发送快速媒体访问控制eMAC报文;在计时至抢占时延目标值时,发送所述eMAC报文。
- 根据权利要求1所述的方法,其中,确定需要发送eMAC报文,包括:若接收到eMAC报文或者帧抢占请求,则确定需要发送eMAC报文。
- 根据权利要求1或2所述的方法,其中,通过以下方式中至少之一确定所述抢占时延目标值:在通信设备启动时根据可被抢占媒体访问控制pMAC报文非最后一个分片的最小值与端口传输速率计算;静态配置;接收网络侧配置;根据帧抢占请求携带的参数配置。
- 根据权利要求1至3中任一项所述的方法,其中,在计时至抢占时延目标值时,发送所述eMAC报文之前,还包括:确认无抖动帧抢占使能参数值有效。
- 根据权利要求4所述的方法,其中,通过以下方式中至少之一确定所述无抖动帧抢占使能参数值:接收控制平面的配置;静态配置;默认值;根据所述抢占时延目标值确定;根据帧抢占请求携带的参数配置。
- 根据权利要求1至5中任一项所述的方法,其中,在计时至抢占时延目标值时,发送所述eMAC报文之前,还包括:若计时未启动,则开始计时;若计时已启动,则判断是否计时至所述抢占时延目标值;在发送完毕所述eMAC报文之后,还包括:计时复位。
- 根据权利要求1至6中任一项所述的方法,其中,还包括:在未计时至所述抢占时延目标值时,继续判断是否计时至所述抢占时延目 标值。
- 根据权利要求1至7中任一项所述的方法,其中,还包括:在当前正在发送报文的情况下,确定发送报文的报文类型;当所述报文类型为pMAC时,打断pMAC报文的传输。
- 根据权利要求8所述的方法,其中,确定发送报文的报文类型,包括:根据报文发送变量值确定发送报文的报文类型;在发送所述eMAC报文之后,以及在发送完毕所述eMAC报文之后,还包括:设置所述报文发送变量值。
- 一种帧抢占装置,包括:eMAC抢占确定模块,设置为确定需要发送eMAC报文;eMAC报文发送模块,设置为在计时至抢占时延目标值时,发送所述eMAC报文。
- 一种通信设备,包括:存储器,以及一个或多个处理器;所述存储器,配置为存储一个或多个程序;当所述一个或多个程序被所述一个或多个处理器执行,使得所述一个或多个处理器实现如权利要求1-9中任一项所述的方法。
- 一种存储介质,所述存储介质存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求1-9中任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/273,821 US20240305573A1 (en) | 2021-03-02 | 2022-02-09 | Frame preemption method and apparatus, device and storage medium |
EP22762357.6A EP4304150A4 (en) | 2021-03-02 | 2022-02-09 | FRAME PRE-AUTHORIZATION METHOD AND DEVICE AND DEVICE AND STORAGE MEDIUM |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110231516.7 | 2021-03-02 | ||
CN202110231516.7A CN115086247A (zh) | 2021-03-02 | 2021-03-02 | 帧抢占方法、装置、设备和存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022183890A1 true WO2022183890A1 (zh) | 2022-09-09 |
Family
ID=83154713
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/075739 WO2022183890A1 (zh) | 2021-03-02 | 2022-02-09 | 帧抢占方法、装置、设备和存储介质 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240305573A1 (zh) |
EP (1) | EP4304150A4 (zh) |
CN (1) | CN115086247A (zh) |
WO (1) | WO2022183890A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115378874B (zh) * | 2022-10-20 | 2023-01-24 | 北京智芯微电子科技有限公司 | 数据发送、接收方法、装置、电子设备、芯片及存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110784418A (zh) * | 2019-10-24 | 2020-02-11 | 烽火通信科技股份有限公司 | 一种基于时延约束的数据发送方法及系统 |
US20200136953A1 (en) * | 2018-10-31 | 2020-04-30 | Keysight Technologies, Inc. | Methods, systems, and computer readable media for testing effects of simulated frame preemption and deterministic fragmentation of preemptable frames in a frame-preemption-capable network |
CN111970271A (zh) * | 2020-08-14 | 2020-11-20 | 苏州盛科科技有限公司 | 一种tsn报文抢占式调度方法及装置 |
CN112105080A (zh) * | 2020-11-18 | 2020-12-18 | 之江实验室 | 一种时间敏感网络数据传输系统及传输方法 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8238324B2 (en) * | 2009-07-24 | 2012-08-07 | Broadcom Corporation | Method and system for network aware virtual machines |
JP6394325B2 (ja) * | 2014-11-26 | 2018-09-26 | 富士通株式会社 | ネットワーク制御方法,通信装置,および通信システム |
EP3503485B1 (en) * | 2017-12-22 | 2023-01-25 | Marelli Europe S.p.A. | Method for managing traffic in a network based upon ethernet switches, vehicle, communication interface, and corresponding computer program product |
CN112671656B (zh) * | 2019-10-16 | 2023-03-10 | 华为技术有限公司 | 一种对网络进行配置的方法和设备 |
WO2021147044A1 (zh) * | 2020-01-22 | 2021-07-29 | 华为技术有限公司 | 一种时间敏感网络时间同步方法及装置 |
CN113852644B (zh) * | 2021-11-26 | 2022-03-01 | 之江实验室 | 一种确定性网络设备识别认证装置及方法 |
-
2021
- 2021-03-02 CN CN202110231516.7A patent/CN115086247A/zh active Pending
-
2022
- 2022-02-09 WO PCT/CN2022/075739 patent/WO2022183890A1/zh active Application Filing
- 2022-02-09 EP EP22762357.6A patent/EP4304150A4/en active Pending
- 2022-02-09 US US18/273,821 patent/US20240305573A1/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200136953A1 (en) * | 2018-10-31 | 2020-04-30 | Keysight Technologies, Inc. | Methods, systems, and computer readable media for testing effects of simulated frame preemption and deterministic fragmentation of preemptable frames in a frame-preemption-capable network |
CN110784418A (zh) * | 2019-10-24 | 2020-02-11 | 烽火通信科技股份有限公司 | 一种基于时延约束的数据发送方法及系统 |
CN111970271A (zh) * | 2020-08-14 | 2020-11-20 | 苏州盛科科技有限公司 | 一种tsn报文抢占式调度方法及装置 |
CN112105080A (zh) * | 2020-11-18 | 2020-12-18 | 之江实验室 | 一种时间敏感网络数据传输系统及传输方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4304150A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP4304150A4 (en) | 2024-07-31 |
EP4304150A1 (en) | 2024-01-10 |
CN115086247A (zh) | 2022-09-20 |
US20240305573A1 (en) | 2024-09-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20060203730A1 (en) | Method and system for reducing end station latency in response to network congestion | |
US7558269B2 (en) | Method for transmitting high-priority packets in an IP transmission network | |
WO2021244240A1 (zh) | 网络拥塞的控制方法、装置、设备、系统及存储介质 | |
WO2019148563A1 (zh) | 一种数据发送方法、接收方法及装置 | |
CN112104562B (zh) | 拥塞控制方法及装置、通信网络、计算机存储介质 | |
CN108833293B (zh) | 一种基于软件定义网络sdn的数据中心拥塞控制方法及装置 | |
CN108989235B (zh) | 一种报文转发控制方法及装置 | |
JP5928764B2 (ja) | 肯定応答パケットを処理するための方法、装置、およびシステム | |
WO2019134383A1 (zh) | 控制网络拥塞的方法、接入设备和计算机可读存储介质 | |
EA010385B1 (ru) | Способ и устройство для изохронной доставки дейтаграмм по каналу передачи данных с конкуренцией | |
JP2009105981A (ja) | 帯域幅制御のためにデータ・パケット送信のタイミングを取る方法及びシステム | |
JP7046979B2 (ja) | データ伝送方法、装置、システム、およびデバイス | |
US8341453B2 (en) | Transmission apparatus that transmits data according to a protocol, and method for measuring time in the transmission apparatus | |
WO2017097201A1 (zh) | 一种数据传输方法、发送装置及接收装置 | |
CN106330742B (zh) | 一种流量控制的方法及网络控制器 | |
US20230139633A1 (en) | Data Packet Sending Method and Apparatus | |
US20150237104A1 (en) | Communication system, communication apparatus, and communication method | |
US8838782B2 (en) | Network protocol processing system and network protocol processing method | |
WO2018076641A1 (zh) | 一种减少时延的方法、装置及存储介质 | |
EP3726787A1 (en) | Data stream sending method, device and system | |
WO2022183890A1 (zh) | 帧抢占方法、装置、设备和存储介质 | |
EP3490293B1 (en) | Data receiving method, data sending method, receiving device and system | |
WO2017091941A1 (zh) | 一种处理业务数据包的方法及装置 | |
JP2007013449A (ja) | シェーパー制御方法、データ通信システム、ネットワークインタフェース装置及びネットワーク中継装置 | |
EP3459216B1 (en) | System and method for mtu size reduction in a packet network |
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: 22762357 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18273821 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022762357 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022762357 Country of ref document: EP Effective date: 20231002 |