Transmitting packets over TSN-aware networks

By extracting and mapping packet service category information of non-TSN-aware networks on network nodes, the problem that TSN-aware network cannot effectively handle non-TSN packets is solved, and seamless interoperability and efficient transmission between non-TSN devices and TSN networks are realized, improving the Network availability and control accuracy.

CN113056892BActive Publication Date: 2024-12-03ABB (SCHWEIZ) AG
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN201880099230.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-11-13
Publication Date
2024-12-03
Estimated Expiration
2038-11-13

AI Technical Summary

Technical Problem

The TSN-aware network cannot effectively perceive and process packets from non-TSN-aware networks, limiting the application of protocols such as industrial Ethernet in TSN networks.

Method used

The network node obtains the service flow of packets from the non-TSN-aware network interface, extracts the service category information, and maps it to the TSN service category or priority, and then transmits the packets to the TSN-aware network after the indicator is associated, and vice versa, realizing Seamless communication between non-TSN devices and TSN networks.

Benefits of technology

It realizes effective transmission and control of non-TSN-aware devices and products in the TSN network, avoids device migration and integration complexity, and ensures high availability and bounded waiting time of the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113056892B_ABST
    Figure CN113056892B_ABST
Patent Text Reader

Abstract

A mechanism for transmitting packets on a TSN-aware network is provided. The method is performed by a network node. The method comprises obtaining (S102) a traffic flow of packets from a non-TSN-aware network interface. The method comprises extracting (S104) information indicating to which traffic class the traffic flow belongs from the packets and above Open Systems Interconnection (OSI) protocol layer 2. The method comprises mapping (S106) the traffic class to a TSN traffic class or priority. The method comprises associating (S108) the packets with an indicator of the TSN traffic class or priority. The method comprises providing (S112) the traffic flow of the packets including the indicator to a TSN-aware network interface for transmitting the packets on the TSN-aware network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments presented herein relate to a method, a network node, a computer program, and a computer program product for transmitting packets on a Time Sensitive Networking (TSN) aware network. Background Art

[0002] In industrial communication networks, obtaining high availability and bounded latency given the communication protocol, its parameters, and the physical environment in which the communication network is deployed can be a challenge.

[0003] For example, TSN is an emerging standard that aims to implement Ethernet with real-time capabilities. TSN enables support for isochronous services, hard and soft real-time services, audio and video services, and best-effort services (to name a few examples). TSN supports different service classes or priorities coexisting on the same network while guaranteeing deterministic end-to-end behavior. The mapping of different service classes and priorities can be performed by assigning so-called VLAN tags (where VLAN is an abbreviation for Virtual Local Area Network) and MAC addresses (where MAC is an abbreviation for Media Access Control) to different priority queues / classes.

[0004] IEEE 802.1Q (commonly referred to as Dot1q) is a networking standard that supports virtual VLANs on IEEE 802.3 Ethernet networks. According to one example, IEEE 802.1Q adds a 32-bit field between the source MAC address and the EtherType field of the original frame. The 32-bit field includes a tag protocol identifier (TPID), tag control information (TCI), a priority code point (PCP), a discard appropriateness indicator (DEI), and a VLAN identifier (VID).

[0005] One problem is as follows: TSN is primarily an Open Systems Interconnection (OSI) protocol layer 2 mechanism, which means that TSN has no awareness of the actual industrial protocol being transmitted on the network. Therefore, protocol layer 2 here refers to layer 2 of the OSI model.

[0006] This means that existing protocols that are not TSN-aware, such as but not limited to PROFINET (short for Process Field Network), which is an industrial technology standard for data communication over Industrial Ethernet, are limited in their means of leveraging any benefits of TSN networks. For example, but not limited to PROFINET, which has cyclical traffic, acyclical traffic, and best-effort traffic at the same time.

[0007] Therefore, there is still a need for improvements in transmitting packets over TSN-aware networks. Summary of the invention

[0008] It is an object of embodiments herein to provide efficient transmission of packets over a TSN-aware network without the problems identified above or at least wherein the problems identified above are mitigated or reduced.

[0009] According to a first aspect, a method for transmitting packets on a TSN-aware network is proposed. The method is performed by a network node. The method comprises obtaining a traffic flow of packets from a non-TSN-aware network interface. The method comprises extracting information indicating to which traffic class the traffic flow belongs from the packets and above OSI protocol layer 2. The method comprises mapping the traffic class to a TSN traffic class or priority. The method comprises associating the packets with an indicator of the TSN traffic class or priority. The method comprises providing the traffic flow of the packets including the indicator to a TSN-aware network interface for transmitting the packets on the TSN-aware network.

[0010] According to a second aspect, a network node for transmitting packets on a TSN-aware network is provided. The network node includes a processing circuit system. The processing circuit system is configured to cause the network node to obtain a traffic flow of packets from a non-TSN-aware network interface. The processing circuit system is configured to cause the network node to extract information indicating which traffic class the traffic flow belongs to from the packet and above OSI protocol layer 2. The processing circuit system is configured to cause the network node to map the traffic class to a TSN traffic class or priority. The processing circuit system is configured to cause the network node to associate the packet with an indicator of the TSN traffic class or priority. The processing circuit system is configured to cause the network node to provide the traffic flow of the packet including the indicator to the TSN-aware network interface for transmitting the packet on the TSN-aware network.

[0011] According to a third aspect, a computer program for transmitting packets on a TSN-aware network is proposed, the computer program comprising a computer program code which, when executed on a network node, causes the network node to perform the method according to the first aspect.

[0012] According to a fourth aspect, a method for receiving packets from a TSN-aware network is provided. The method is performed by a network node. The method comprises obtaining a traffic flow of packets from a TSN-aware network interface, wherein the packets comprise an indicator of a TSN traffic class or priority for the traffic flow. The method comprises removing the indicator. The method comprises providing the traffic flow of packets without the indicator thus removed to a non-TSN-aware network interface.

[0013] According to a fifth aspect, a network node for receiving packets from a TSN-aware network is provided. The network node comprises a processing circuit system. The processing circuit system is configured to cause the network node to obtain a traffic flow of packets from a TSN-aware network interface, wherein the packets comprise an indicator of a TSN traffic class or priority for the traffic flow. The processing circuit system is configured to cause the network node to remove the indicator. The processing circuit system is configured to cause the network node to provide the traffic flow of packets without the indicator thus removed to a non-TSN-aware network interface.

[0014] According to a sixth aspect, a computer program for receiving packets from a TSN aware network is proposed, the computer program comprising a computer program code which, when run on a network node, causes the network node to perform the method according to the fourth aspect.

[0015] According to a seventh aspect, a computer program product is provided, the computer program product comprising a computer program according to at least one of the third aspect and the sixth aspect and a computer readable storage medium on which the computer program is stored. The computer readable storage medium may be a non-transitory computer readable storage medium.

[0016] Advantageously, embodiments disclosed herein provide for efficient transmission of packets over a TSN-aware network, where the packets originate from a non-TSN-aware network interface.

[0017] Advantageously, by using the proposed transmission of packets over a TSN-aware network, the above-mentioned problems may be avoided.

[0018] Advantageously, embodiments disclosed herein enable efficient and fine-grained control of traffic flows from non-TSN-aware devices and products.

[0019] Advantageously, embodiments disclosed herein enable simple migration of non-TSN aware devices and products to TSN networks.

[0020] Advantageously, embodiments disclosed herein enable tight integration of non-TSN aware devices and products into a TSN network.

[0021] Advantageously, the embodiments disclosed herein enable separation of non-TSN aware devices and products from the TSN network, requiring network nodes to be reconfigured only as TSN standards evolve.

[0022] Other objectives, features and advantages of the accompanying embodiments will become apparent from the following detailed description, the attached dependent claims and the accompanying drawings.

[0023] In general, unless otherwise expressly defined herein, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field. Unless otherwise expressly stated, all references to "a / an / the element, device, component, device, module, step, etc." are to be publicly interpreted as referring to at least one instance of an element, device, component, device, module, step, etc. Unless expressly stated otherwise, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Now, the concept of the present invention will be described by way of example with reference to the accompanying drawings, in which:

[0025] Figure 1 is a schematic diagram illustrating a network according to an embodiment;

[0026] Figure 2 and Figure 5 is a flow chart of a method according to an embodiment;

[0027] Figure 3 and Figure 4 is an example of a frame structure for a packet;

[0028] Figure 6 and Figure 7 Schematically illustrates a service flow according to an embodiment;

[0029] Figure 8 is a schematic diagram illustrating functional units of a network node according to an embodiment;

[0030] Fig. 9 is a schematic diagram illustrating functional modules of a network node according to an embodiment; and

[0031] Fig.10 An example of a computer program product including a computer-readable storage medium according to an embodiment is shown. DETAILED DESCRIPTION

[0032] Now, the inventive concept is described more fully below with reference to the accompanying drawings, in which certain embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that the disclosure will be thorough and complete and the scope of the inventive concept will be fully conveyed to those skilled in the art. Throughout the specification, the same reference numerals refer to the same elements. Any steps or features illustrated by dashed lines should be considered optional.

[0033] The problem of transmitting packets from a non-TSN aware network interface over a TSN aware network has been disclosed above.

[0034] Therefore, the embodiments disclosed herein relate to a mechanism for transmitting packets on a TSN-aware network. To obtain such a mechanism, a network node 200a, a method performed by the network node 200a, and a computer program product are provided, the computer program product including, for example, a code in the form of a computer program, which, when executed on the network node 200a, causes the network node 200a to perform the method.

[0035] Figure 1 The network 100 is schematically illustrated in which network nodes 200a, 200b are provided to enable traffic flows of non-TSN systems to utilize TSN mechanisms. The network 100 includes a TSN switch 130 configured to exchange packets of traffic flows between other network entities. The TSN switches 130 together constitute a TSN-aware network 160.

[0036] The network 100 includes a TSN talker 110 and a TSN listener 120. In general, the TSN talker 110 can be any entity that has packets to transmit and is configured to map the packets to different traffic classes and priorities on a TSN-aware network. In general, the TSN listener 120 can be any entity that has packets to receive and is configured to receive packets that have been mapped to different traffic classes and priorities on a TSN-aware network. The same entity can selectively act as a TSN talker 110 or a TSN listener 120 depending on whether the entity has packets to send or packets to receive.

[0037] The network 100 also includes a non-TSN speaker / system 140 and a non-TSN listener / system 150. When sending packets from the non-TSN speaker / system 140 and the non-TSN listener / system 150, the non-TSN speaker / system 140 and the non-TSN listener / system 150 also utilize the TSN switch 130. The non-TSN speaker / system 140 and the non-TSN listener / system 150 are not aware of the underlying TSN mechanism and thus cannot identify packets or map packets to different traffic classes and priorities on the TSN-aware network. The same entity can selectively act as a non-TSN speaker / system 140 or a non-TSN listener / system 150 depending on whether the entity has packets to send or packets to receive. The non-TSN speaker / system 140 and the non-TSN listener / system 150 together constitute a non-TSN-aware network 170. Individually, each of the non-TSN speaker / system 140 and the non-TSN listener / system 150 can therefore constitute or include a non-TSN-aware network interface. Every non-TSN-aware network interface can be an interface to industrial equipment.

[0038] The network 100 also includes network nodes 200a, 200b. The network nodes 200a, 200b interface with both the TSN-aware network 160 and the non-TSN-aware network 170. The portion of the TSN-aware network 160 that interfaces with the network nodes 200a, 200b is referred to as a TSN-aware network interface. Therefore, any TSN switch 130 that interfaces with the network nodes 200a, 200b can be referred to as constituting or including a TSN-aware network interface. The portion of the non-TSN-aware network 170 that interfaces with the network nodes 200a, 200b is referred to as a non-TSN-aware network interface. In short, the network nodes 200a, 200b provide a mapping between a non-TSN-aware protocol and a TSN-aware protocol at runtime, so that packets of the non-TSN-aware protocol can be mapped to appropriate TSN service classes or priorities.

[0039] although Figure 1 One TSN talker 110, one TSN listener 120, one non-TSN talker / system 140, one non-TSN listener / system 150, two network nodes 200a, 200b, and four TSN switches 130 are illustrated, but the embodiments disclosed herein are not limited to any particular number of these entities as long as each non-TSN talker / system 140 and each non-TSN listener / system 150 interfaces with the TSN switch 130 via the network node 200a.

[0040] Figure 2 is a flow chart illustrating an embodiment of a method for transmitting packets over a TSN aware network 160. The method is performed by a network node 200a at runtime. The method is advantageously performed by a network node 200a executing one or more computer programs 1020a.

[0041] Some of these embodiments are based on providing a transparent way to map business flows of non-TSN-aware protocols to TSN protocols at runtime, thereby enabling existing non-TSN-aware systems and products to be effectively migrated to TSN-aware networks.

[0042] Assume that the network node 200a obtains a packet to be transmitted on the TSN-aware network 160 from a non-TSN-aware network interface. Therefore, the network node 200a is configured to perform step S102:

[0043] S102: The network node 200a obtains a packetized service flow from a non-TSN-aware network interface.

[0044] The network node 200a uses information from layers above OSI layer 2 to map the packets to appropriate TSN service classes or priorities according to their different service classes. Therefore, the network node 200a is configured to perform steps S104 and S106:

[0045] S104: The network node 200a extracts information indicating to which service category the service flow belongs from the packet and above OSI protocol layer 2.

[0046] Examples of such business categories are given below.

[0047] S106: The network node 200a maps the service class to a TSN service class or priority.

[0048] In order for the TSN-aware network 160 to handle packets according to TSN service class or priority, the packets are associated with corresponding indicators. Therefore, the network node 200a is configured to perform step S108:

[0049] S108: The network node 200a associates the packet with an indicator of the TSN service class or priority.

[0050] Examples of such indicators are given below.

[0051] These packets are then ready to be handled on the TSN-aware network 160. Therefore, the network node 200a is configured to perform step S112:

[0052] S112 : The network node 200 a provides a traffic flow of packets including the indicator to the TSN-aware network interface for transmitting the packets on the TSN-aware network 160 .

[0053] The network node 200a thus enables existing non-TSN-aware systems and products to be efficiently migrated to a TSN-aware network without compromising any warranty or any changes to the existing non-TSN-aware systems and products. The network node 200a thus enables non-TSN speakers / systems to coexist with TSN speakers 110s and TSN listeners 120s. In this way, non-TSN-aware systems and products can take advantage of TSN features such as seamless redundancy, bounded latency, and time synchronization. In some aspects, the network node 200a can therefore be considered a TSN enabler.

[0054] Embodiments related to further details of transmitting packets over the TSN-aware network 160 as performed by the network node 200a are now disclosed.

[0055] There may be different types of traffic classes to which a traffic flow may belong. According to some non-limiting examples, the traffic class of the non-TSN aware protocol to which the traffic flow belongs is a round-robin type, an acyclic type, or a best effort type.

[0056] In step S108, there may be different types of indicators of TSN service class or priority with which the network node 200a associates the packet. In one example, the indicator is a VLAN tag. Thus, in some aspects, after having been associated with the indicator, the packet is considered to be VLAN-tagged.

[0057] Figure 3 An example of a frame structure 300 of an Ethernet frame used in an IEEE 802.1Q VLAN tagging scheme is given. The frame structure 300 includes a preamble field, a destination media access control (MAC) address field, a source MAC address field, an 802.1Q header field, an EtherType size field, a payload field, a cyclic redundancy check / frame check sequence (CRC / FCS) field, and an interframe gap field. Since the VLAN tag itself is attached to the frame rather than implied by the content of the frame (implicit VLAN tagging scheme), this tagging scheme is an example of an explicit VLAN scheme. A four-byte tag is inserted immediately after the source address and before the type / length field. The first two bytes are called the tag protocol identifier, which functions very similarly to the type / length field. The content of the two bytes is set to a value of 0x8100, which is to be identified as a VLAN tag. The following two bytes are tag control information. The rest of the Ethernet frame remains unchanged, except that the frame check sequence (FCS) must be recalculated because the frame is longer. In addition to this constraint, VLAN tags can be added or removed without affecting the content or nature of the message. The two-byte tag control information consists of three bits for the IEEE 802.1p priority level (that is, independent of VLAN): one bit called the Canonical Format Indicator (CFI) and 12 bits for the VLAN identifier. If 12 bits of the identifier are used, a maximum of 4096 VLANs can exist. However, the "all-one" sequence is reserved and the "all-zero" sequence indicates that no VLAN association is made, which means that the VLAN tag is only used to indicate the priority level. All other identifiers can be used to indicate a specific VLAN as well as the 802.1p priority level of the message. The CFI bit is used to indicate the bit ordering within the frame, which is a problem when communicating over a non-Ethernet Local Area Network (LAN).

[0058] In some aspects, in order to comply with TSN standards (e.g., timing, scheduling, latency, bandwidth, etc.), the network node 200a buffers packets in a queue and forwards packets only according to a given TSN-aware network configuration. Specifically, according to one embodiment, the network node 200a is configured to perform optional step S110:

[0059] S110 : Before providing a traffic flow of packets including the indicator to the TSN-aware network interface, the network node 200 a buffers the packets. The packets are buffered according to the network configuration of the TSN-aware network 160 .

[0060] When executed, step S110 is performed between steps S108 and S112 described above.

[0061] The network node 200a can be scheduled on the TSN-aware network and can also request resources from the TSN-aware network to meet the requirements of its non-TSN-aware speaker / system. In some aspects, the network node 200a is configured to achieve this by inspecting the packets and mapping the identified information to the appropriate TSN service. That is, according to one embodiment, the information indicating which service class the service flow belongs to is extracted through packet inspection or even deep packet inspection. Further, in this aspect, the information indicating which service class the service flow belongs to can be extracted from the packet header of the packet. Further, in this aspect, the extracted information can identify the non-TSN-aware protocol used by the non-TSN-aware network interface for the service flow.

[0062] Figure 4 An example of a frame structure 400 of a conventional Ethernet frame that is not suitable for VLAN tagging is given. The frame structure 400 includes a preamble field, a destination MAC address field, a source MAC address field, an EtherType size field, a payload field, and a CRC / FCS field. In this regard, reference is made to Figure 4 , the protocol type can be identified by examining the EtherType field. In general, the EtherType field is used to indicate which protocol is encapsulated in the payload of the frame. The same field is also used to indicate the size of some Ethernet frames. The data link layer uses this field to determine which protocol to switch the payload on the receiving end. Thereafter, the protocol specific information above the OSI protocol layer 2 can be extracted in order to classify into which service class the packet should be mapped to. In addition, in the case of an aggregated payload, each individual packet can be identified and extracted into a new smaller packet with the corresponding service class type. The process is repeated until the received frame ends.

[0063] In some aspects, this information is therefore defined by the protocol used at a higher protocol layer. According to a first embodiment, the information is extracted at OSI protocol layer 7, and according to a second embodiment, the information is extracted at OSI protocol layer 3 or 4. The packet inspection results can then be provided down to OSI protocol layer 2, where the information will ensure that the correct TSN parameters are associated with the packet. This is Figure 3 and Figure 4 As schematically shown in Figure 3 and Figure 4The diagram shows the traffic flow of packets in the corresponding protocol stack of the network node 200a. Figure 6 and Figure 7 In both, as in step S112, the service flow is provided to the TSN-aware network interface at OSI protocol layer 2.

[0064] In some aspects, the network node 200a may obtain, but is not limited to, serial data that the network node 200a will encapsulate and send from, for example, an RS485 interface (also known as TIA-485(-A) or EIA-485) on the TSN-aware network 160 according to the TSN standard. That is, according to one embodiment, the non-TSN-aware network interface is an RS-485 interface. Further, then, in step S102, the service flow may be obtained as serial data on the RS-485 interface.

[0065] Figure 5 is a flow chart illustrating an embodiment of a method for receiving packets from a TSN aware network 160. The method is performed by a network node 200b at runtime. The method is advantageously performed by a network node 200b executing one or more computer programs 1020b.

[0066] The network node 200a is configured to handle a traffic flow of packets from the TSN-aware network 160 and destined for the non-TSN-aware network 170. In particular, the network node 200b is configured to perform optional step S202:

[0067] S202: The network node 200b obtains a packetized service flow from a TSN-aware network interface. The packet includes an indicator of a TSN service class or priority for the service flow.

[0068] Then, the indicator is removed by the network node 200b. That is, the network node 200b is configured to perform optional step S204:

[0069] S204: The network node 200b removes the indicator.

[0070] Then, the packet is provided to the non-TSN aware network 170. That is, the network node 200b is configured to perform optional step S206:

[0071] S206: The network node 200b provides the traffic flow of packets without the thus removed indicator to the non-TSN aware network interface.

[0072] The network node 200b thereby enables non-TSN listeners / systems to coexist with TSN talkers and listeners.

[0073] As disclosed above, according to one embodiment, the non-TSN-aware network interface is an RS-485 interface. Therefore, in step S206, the service flow may be provided as serial data on the RS-485 interface.

[0074] Figure 6 An embodiment is schematically illustrated wherein a traffic flow is acquired from a non-TSN aware network interface at OSI protocol layer 1, wherein information is extracted at OSI protocol layer 4, and wherein at OSI protocol layer 2 an indicator is associated with a packet comprising down stack communications from OSI protocol layer 4 to OSI protocol layer 2. This may represent a scenario wherein the traffic flow is an Ethernet traffic flow.

[0075] Figure 7 An embodiment is schematically illustrated, wherein a traffic flow is obtained from a non-TSN aware network interface at OSI protocol layer 7, wherein information is extracted at OSI protocol layer 3, 4 or 7, and wherein an indicator is associated with a packet at OSI protocol layer 2, the packet comprising down stack communication from OSI protocol layer 7 to OSI protocol layer 2. This may represent a scenario where the traffic is a non-Ethernet traffic flow.

[0076] Figure 8 The components of the network nodes 200a, 200b according to an embodiment are schematically illustrated in terms of several functional units. The processing circuit system 210 uses a computer program product 1010a, 1010b10 (eg, Fig.10 The processing circuit system 210 may be any combination of one or more of the following items of software instructions in the form of a suitable central processing unit (CPU), a multiprocessor, a microcontroller, a digital signal processor (DSP), etc. For example, the processing circuit system 210 may also be provided as at least one application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0077] In particular, the processing circuit system 210 is configured to cause the network nodes 200a, 200b to perform a set of operations or steps as disclosed above. For example, the storage medium 230 may store the set of operations, and the processing circuit system 210 may be configured to retrieve the set of operations from the storage medium 230 to cause the network nodes 200a, 200b to perform the set of operations. The set of operations may be provided as a set of executable instructions.

[0078] Therefore, the processing circuit system 210 is thereby arranged to perform the method disclosed herein. The storage medium 230 may also include permanent storage, which may be, for example, any single item or combination of the following: magnetic storage, optical storage, solid-state storage, or even remotely mounted storage. The network node 200a, 200b may also include a communication interface 220, which is at least configured to communicate with other nodes, functions, entities, and devices of the network 100. Therefore, the communication interface 220 may include one or more transmitters and receivers, which include analog components and digital components. The processing circuit system 210 controls the general operation of the network node 200a, 200b, for example, by the following items: sending data signals and control signals to the communication interface 220 and the storage medium 230, receiving data and reports from the communication interface 220, and retrieving data and instructions from the storage medium 230. The other components and related functionality of the network node 200a, 200b are omitted to avoid blurring the concepts proposed herein.

[0079] Fig. 9 The components of the network nodes 200a, 200b according to the embodiment are schematically illustrated in terms of several functional modules. Figure 2 When the method is used, the network nodes 200a and 200b include an acquisition module 210a, which is configured to perform step S102; an extraction module 210b, which is configured to perform step S104; a mapping module 210c, which is configured to perform step S106; a providing module 210f, which is configured to perform step S112; and an optional buffer module 210e, which is configured to perform step S110. When configured to perform according to Figure 5 When the method is performed, the network nodes 200a and 200b include a providing module 210g, which is configured to perform step S202; a removing module 210h, which is configured to perform step S204; and an obtaining module 210i, which is configured to perform step S206. In some aspects, the same network node 200a and 200b is configured to perform the steps according to Figure 2 Methods and basis Figure 3 Both methods therefore include all functional modules 210a to 210i.

[0080] In general, in one embodiment, each functional module 210a to 210i may be implemented solely in hardware, and in another embodiment, may be implemented with the aid of software, that is, the latter embodiment has computer program instructions stored on the storage medium 230, which, when executed on the processing circuit system, causes the network nodes 200a, 200b to perform the above-mentioned combined Fig. 9 The corresponding steps mentioned. It should also be mentioned that even if the modules correspond to parts of a computer program, they are not necessarily separate modules therein, but the way they are implemented in software depends on the programming language used. Preferably, one or more or all of the functional modules 210a to 210i can be implemented by the processing circuit system 210, which can cooperate with the communication interface 220 and / or the storage medium 230. Therefore, the processing circuit system 210 can be configured to obtain instructions as provided by the functional modules 210a to 210i from the storage medium 230 and execute these instructions, thereby performing any steps as disclosed herein.

[0081] The network nodes 200a, 200b may be provided as a standalone device or as part of at least one other device. For example, the network nodes 200a, 200b may be provided as an external device that is disposed at an interface between a non-TSN-aware network and a TSN-aware network interface, the non-TSN-aware network including the non-TSN-aware network interface. Alternatively, the network nodes 200a, 200b may be implemented as a virtual network function of a switch that operates at an interface between a non-TSN-aware network including the non-TSN-aware network interface and the TSN-aware network interface.

[0082] Fig.10 An example of a computer program product 1010a, 1010b including a computer-readable storage medium 1030 is shown. On the computer-readable storage medium 1030, a computer program 1020a, 1020b may be stored that may cause the processing circuit system 210 and entities and devices operatively coupled to the processing circuit system (such as the communication interface 220 and the storage medium 230) to perform methods according to the embodiments described herein. Thus, the computer program 1020a, 1020b and / or the computer program product 1010a, 1010b may provide a means for performing any of the steps disclosed herein.

[0083] exist Fig.10In the example of , the computer program products 1010a, 1010b are illustrated as an optical disc such as a CD (Compact Disc) or a DVD (Digital Versatile Disc) or a Blu-ray Disc. The computer program products 1010a, 1010b may also be implemented as a memory such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM), more particularly, as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a flash memory such as a compact flash. Thus, although the computer programs 1020a, 1020b are schematically illustrated herein as tracks on the depicted optical disc, the computer programs 1020a, 1020b may be stored in any manner suitable for the computer program products 1010a, 1010b.

[0084] The inventive concept has been described above mainly with reference to some embodiments. However, as will be readily appreciated by a person skilled in the art, other embodiments than those disclosed above are equally possible within the scope of the inventive concept as defined by the appended patent claims.

Claims

1. A method for transmitting packets on a time-sensitive network (TSN)-aware network (160), the method being performed by a network node (200a), the method include: Acquire (S102) a packetized service flow from a non-TSN-aware network interface, wherein the service flow is acquired from the non-TSN-aware network interface at OSI protocol layer 1; extracting (S104) from the packet and above Open Systems Interconnection (OSI) protocol layer 2 information indicating to which service class the service flow belongs, wherein the extracted information identifies a non-TSN-aware protocol used by the non-TSN-aware network interface for the service flow; Mapping (S106) the service class to a TSN service class or priority; associating the packet with an indicator of the TSN service class or priority (S108); and A traffic flow of the packet including the indicator is provided (S112) to a TSN-aware network interface for transmitting the packet over the TSN-aware network (160).

2. The method according to claim 1, further comprising: include: Before providing a traffic flow of the packets including the indicator to the TSN-aware network interface, the packets are buffered (S110), and wherein the packets are buffered according to a network configuration of the TSN-aware network (160). The method according to claim 1 or 2, wherein the indicator is a Virtual Local Area Network (VLAN) tag. 4 . The method according to claim 1 , wherein the information indicating to which traffic class the traffic flow belongs is extracted through packet inspection or deep packet inspection.

5. The method according to claim 1, wherein the information indicating to which traffic class the traffic flow belongs is extracted from a packet header of the packet. The method of claim 1 , wherein the information is extracted at OSI protocol layer 7.

7. The method of claim 1, wherein the information is extracted at OSI protocol layer 3 or 4.

8. The method according to claim 1, wherein the service category of the non-TSN-aware protocol to which the service flow belongs is a round-robin type, a non-round-robin type, or a best-effort type.

9. The method of claim 1, wherein the traffic flow is an Ethernet traffic flow.

10. The method of claim 1, wherein the traffic flow is a non-Ethernet traffic flow.

11. The method of claim 1, wherein the traffic flow is acquired from the non-TSN aware network interface at OSI protocol layer 7.

12. The method of claim 1, wherein the non-TSN aware network interface is an RS-485 interface.

13. The method of claim 12, wherein the traffic stream is acquired as serial data on the RS-485 interface.

14. The method of claim 1, wherein the traffic flow is provided to the TSN-aware network interface at OSI protocol layer 1.

15. The method according to claim 1, wherein the network node (200a) is an external device, which is arranged at an interface between a non-TSN network and the TSN-aware network interface, and the non-TSN network includes the non-TSN-aware network interface.

16. The method of claim 1, wherein the network node (200a) is implemented as a virtual network function of a switch, the switch operating at an interface between a non-TSN network and the TSN-aware network interface, the non-TSN network including the non-TSN-aware network interface.

17. The method of claim 1, wherein the non-TSN-aware network interface is an interface to industrial equipment.

18. A network node (200a) for transmitting packets on a time sensitive network (TSN) aware network (160), the network node (200a) comprising a processing circuit system (210), the processing circuit system being configured to cause the network node (200a) to: Acquire a packetized traffic flow from a non-TSN-aware network interface, wherein the traffic flow is acquired from the non-TSN-aware network interface at OSI protocol layer 1; extracting information indicating to which traffic class the traffic flow belongs from the packet and above Open Systems Interconnection (OSI) protocol layer 2, wherein the extracted information identifies a non-TSN aware protocol used by the non-TSN aware network interface for the traffic flow; Mapping the service class to a TSN service class or priority; associating the packet with an indicator of the TSN traffic class or priority; as well as A traffic flow of the packets including the indicator is provided to a TSN-aware network interface for transmission of the packets over the TSN-aware network (160).

19. The network node (200a) according to claim 18, further configured to perform the method according to any one of claims 2 to 17.

20. A computer readable storage medium having stored thereon a computer program (1020a) for transmitting packets on a time sensitive network (TSN) aware network (160), the computer program comprising computer code which, when executed on a processing circuitry (210) of a network node (200a), causes the network node (200a) to: Acquire (S102) a packetized service flow from a non-TSN-aware network interface, wherein the service flow is acquired from the non-TSN-aware network interface at OSI protocol layer 1; extracting (S104) from the packet and above Open Systems Interconnection (OSI) protocol layer 2 information indicating to which service class the service flow belongs, wherein the extracted information identifies a non-TSN-aware protocol used by the non-TSN-aware network interface for the service flow; Mapping (S106) the service class to a TSN service class or priority; associating the packet with an indicator of the TSN traffic class or priority; as well as A traffic flow of the packet including the indicator is provided (S112) to a TSN-aware network interface for transmitting the packet over the TSN-aware network (160).

21. A computer program product (1010a, 1010b), comprising a computer-readable storage medium (1030) according to claim 20, and a computer program (1020a, 1020b) stored on the computer-readable storage medium.

Citation Information

Patent Citations

  • Method for mapping service flow to service transmission path and optical network terminal

    CN101005445A

  • System and method for implementing self-governing QoS based on service network differentiation and IPv6 spreading head

    CN101510846A

  • Service forwarding and priority mapping method for China-data over cable system interface specification (C-DOCSIS) system

    CN102546118A

  • Data link layer protocol unit, mobile radio devices, mobile radio network control unit and method for reading data from a plurality of data link layer protocol buffer storages

    CN102740503A

  • Data security level agreement unit, related device and method

    CN1767535A