WO2020128683A1

WO2020128683A1 - A device and method for scheduling data transmission for non-tsn devices over time sensitive networking (tsn)

Info

Publication number: WO2020128683A1
Application number: PCT/IB2019/060113
Authority: WO
Inventors: Ravish Kumar; Mallikarjun Kande; Srini Ramaswamy
Original assignee: ABB Schweiz AG
Current assignee: ABB Schweiz AG
Priority date: 2018-12-18
Filing date: 2019-11-25
Publication date: 2020-06-25
Anticipated expiration: 2021-06-18

Abstract

The present, disclosure discloses an intermediate Time Sensitive Networking (TSN) device (101) and method for scheduling data transmission for non-TSN devices over TSN (101). The intermediate TSN device (101) determines Media Access Control (MAC) address details for a non-TSN device of a plurality of non-TSN devices (107) by monitoring data traffic associated with the non-TSN device. The intermediate TSN device (101) generates configuration data using a TSN policy associated with the non-TSN device. The TSN policy associated with the non-TSN de vice is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device, where the plurality of TSN policies is generated based on communication traffic data between the talker devices and the associated listener devices and attributes associated with each communication type. Thereafter, the intermediate TSN device (101) transmit the configuration data to the CUC which initiates configuration with CNC of TSN based on the configuration data for scheduling the data transmission.

Description

A DEVICE AND METHOD FOR SCHEDULING DATA TRANSMISSION FOR NON-TSN DEVICES OVER TIME SENSITIVE NETWORKING (TSN)

TECHNICAL FIELD

[001] The present disclosure relates in general to network communication. More particularly, the present disclosure relates to a device and method for scheduling data transmission for non- Time Sensitive Networking (TSN) devices over TSN.

BACKGROUND

[002] In recent past, industrial communication has undergone tremendous changes. With introduction of Time Sensitive Networking (TSN) in the communication network, Industrial Control System (ICS) has benefitted from use of TSN in their systems by accessing a network that promises reduced latency, shared synchronized time, and convergence of control traffic and standard ethemet traffic. The TSN is a key for industrial applications such as process and machine control, where low communication latency and minimal jitter are critical for meeting closed loop control requirements. The TSN is the first fully open, standard and interoperable way to fulfil these requirements.

[003] Traditional automation devices may not have capability related to the TSN Protocol.

This lack of capability in traditional automation devices may inhibit deterministic information flows over ethemet.

[004] Thus, the traditional automation devices require additional devices, such as TSN gateways for connecting devices which do not have TSN implementation (i.e. non- TSN devices) to the TSN. However, such TSN gateways demand complex workflows and engineering. In addition, the TSN gateways are vendor-specific and need configurations proposed by vendors. Such vendor specific configurations may not integrate well with engineering tools, thus making the use of such TSN gateways highly complex.

SUMMARY

[005] The present disclosure discloses an intermediate Time Sensitive Networking (TSN) device for scheduling data transmission for non-TSN devices over TSN. [006] In an embodiment, an intermediate Time Sensitive Networking (TSN) device is configured in a TSN for scheduling data transmission for non-TSN devices over the TSN. The TSN comprises a Centralized User Configuration (CUC) and a Centralized Network Configuration (CNC) for scheduling data transmission, and one or more end point devices. The one or more end point devices comprise talker devices and associated listener devices. The intermediate TSN device is connected between at least one of a plurality of TSN devices and non-TSN devices with a plurality' of non-TSN devices. The intermediate TSN device is configured to determine Media Access Control (MAC) address details for a non-TSN device of the plurality of non-TSN devices by monitoring data traffic associated with the non-TSN device. Further, the intermediate TSN device generates configuration data using a TSN policy associated with the non-TSN device. The TSN policy associated with the non-TSN device is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device. In an embodiment, the plurality of TSN policies is generated based on communication traffic data between the talker devices and the associated listener devices and attributes associated with each communication type. On generating the configuration data, the intermediate TSN device transmit the configuration data to the CUC, which initiates configuration with the CNC based on die configuration data and schedules the data transmission.

[007] In an implementation, the present disclosure may relate to a method for enabling realtime data communication over Time Sensitive Networking (TSN) for non-TSN devices. The TSN comprises a plurality of intermediate TSN devices connected between at least one of a plurality of TSN devices and non-TSN devices with a plurality of non-TSN devices. Each of the plurality of intermediate TSN devices is configured to determine Media Access Control (MAC) address details for a non-TSN device of the plurality of non-TSN devices by monitoring data traffic associated with the non-TSN device. Further, configuration data is generated using a TSN policy associated with the non-TSN device. The TSN policy is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device. In an embodiment, the plurality of TSN policies is generated based on communication traffic data between the talker devices and associated listener devices and attributes associated with each communication type. Upon generation of the configuration data, each of the plurality of intermediate TSN devices is configured to transmit the configuration data to the CUC. The CUC initiate configuration with the CNC based on the configuration data for scheduling the data transmission.

[008] In an implementation, the present disclosure may relate to a Time Sensitive Networking (TSN) comprising a Centralized User Configuration (CUC) and a Centralized Network Configuration (CNC) for scheduling data transmission, and one or more end point devices. The one or more end point devices comprise talker devices and associated listener devices. The TSN comprises a plurality of intermediate TSN devices for enabling the data communication over TSN for non-TSN devices. The plurality of intermediate TSN devices are connected between at least one of a plurality of TSN devices and non-TSN devices with a plurality of non-TSN devices. Each of the plurality of intermediate TSN devices is configured to determine Media Access Control (MAC) address details for a non-TSN device of the plurality' of non-TSN devices by monitoring data traffic associated with the non-TSN device. Configuration data is generated using a TSN policy associated with the non-TSN device. The TSN policy is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device. Thereafter, the configuration data is transmitted to the CUC, where the CUC initiate configuration with the CNC based on the configuration data for scheduling the data transmission.

[009] In an embodiment, the plurality of TSN policies is generated using engineering data associated with the plurality of non-TSN devices. Initially, the plurality of TSN policies is generated by identifying the plurality of non-TSN devices to be at least one of the talker devices and listener devices. The communication traffic between the talker devices and the listeners devices is categorized to be one of a predefined communication type. Thereby, generating the plurality of TSN policies based on the communication traffic between the talker devices and the listener devices and attributes associated with each communication type.

[010] In an embodiment, the plurality' of TSN policies is deployed in the intermediate TSN device.

[011] In an embodiment, the plurality of TSN policies are fetched from tire plurality of non-

TSN devices on a request. [012] In an embodiment, the intermediate TSN device stores MAC address of other intermediate TSN devices configured in the TSN and non-TSN device connected to each of the other intermediate TSN devices in a routing table configured in the intermediate TSN device. The intermediate TSN device receives MAC address of other intermediate TSN devices and the non-TSN device connected to each of the other intermediate TSN devices in response to a broadcast message sent by the intermediate TSN device when connected to the TSN.

[013] In an embodiment, the intermediate TSN device broadcasts a request for determining MAC address for a target non-TSN device to other intermediate TSN devices configured in tire TSN when the destination MAC address is not found in the routing table and receives the MAC address from one of the other intermediate TSN devices. In an embodiment, each of the other intermediate TSN devices check MAC address of the target non TSN device and the one of the other intermediate TSN devices provides the MAC address to the intermediate TSN device on identification.

[014] In an embodiment, an industrial control system comprises the intermediate TSN device for scheduling data transmission for non-TSN devices over the TSN.

BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS

[015] FIG.la illustrates an exemplary' environment for scheduling data transmission for non-TSN devices over TSN in accordance with an embodiment of the present disclosure;

[016] FIG.lb illustrates a block diagram of an intermediate TSN device in accordance with an embodiment of the present disclosure;

[017] FIG.2a shows a sequence diagram for generating TSN configuration for scheduling data transmission for non-TSN devices over TSN in accordance with an embodiment of the present disclosure;

[018] FIG.2b illustrates a flowchart illustrating generation of TSN policies in accordance with an embodiment of the present disclosure; [019] FIGJa and Fig.3b illustrate an exemplary embodiment of discovering intermediate TSN devices in TSN in accordance with an embodiment of the present disclosure; and

[020] FIG.4 illustrates a flowchart for predicting for scheduling data transmission for non- TSN devices over TSN in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

[021] In an embodiment, the present di sclosure discloses a method and an intermediate Time Sensitive Networking (TSN) device for scheduling data transmission for non-TSN devices over the TSN. In an embodiment, the TSN is configured with a plurality of intermediate TSN devices for scheduling the data transmission. The present disclosure provides dynamic configuration of intermediate TSN device without complex mechanism. The present disclosure enables non-TSN devices capable of scheduling data transmission over TSN without making any alternation in the network configuration. Therefore, the intermediate TSN device of industrial control system configured in the TSN generate a plurality of TSN policies based on engineering data for the non-TSN devices.

[022] In an embodiment, the engineering data may comprise standard data associated with communication devices. For example, type of devices, type of protocols used by the devices, logic functions, update rate for the devices and the like. A person skilled in the art would understand that the engineering data may also include any other information relates to the devices, not mentioned herein explicitly. The plurality of TSN policies and communication information associated with the non-TSN devices facilitates in scheduling data transmission for the non-TSN devices. Therefore, the present disclosure enables automated configuration of intermediate TSN device which minimizes configuration complexity. Also, the method disclosed in the present disclosure eliminates complex vender-specific gateways and incompatible protocols, thereby enabling data transmission over the TSN for non-TSN devices.

[023] FIG.la illustrates an exemplary environment for scheduling data transmission for non-TSN devices over TSN in accordance with an embodiment of the present disclosure.

[024] As shown in Fig la, an environment 100 includes an intermediate Time Sensitive Networking (TSN) device lOh, an intermediate TSN device lOlz, . and an intermediate TSN device 101 N (collectively referred as plurality of intermediate TSN devices 101) and a TSN device 105i, a TSN device

1052, and a TSN device 105N (collectively referred as plurality of TSN devices 105) connected to a TSN 103. In an embodiment, the TSN 103 refers to a set of standards which define mechanisms for time-sensitive transmission of data over Ethernet networks. The TSN 103 comprises a Centralized User Configuration (CUC), a Centralized Network Configuration (CNC) and one or more end point devices (not shown explicitly in Fig. la). A person skilled in the art would understand that the TSN 103 may comprises other units not mentioned herein explicitly. In an embodiment, the CUC is an application that communicates wife fee CNC and fee end devices. The CUC makes requests to fee CNC for deterministic communication. In an embodiment, fee CNC defines schedule on which TSN flames are transmitted. The one or more end point devices may refer to source and destinations of fee TSN 103. The one or more end point devices may comprise talker devices and listeners devices.

[025] In an embodiment, fee talker devices and fee listener devices are fee devices within fee TSN 103 feat establishes a communication link (also referred to as a virtual link) through which data or information is communicated between a writer and a reader. For example, a talker device may send an advertise signal to a listener device requesting that a communication link be established between fee talker device and fee listener device. In case, if there are enough resources for communicating data from fee talker device to fee listener device (e.g., sufficient bandwidth, available routers and/or switches, etc.), then fee communication link between fee talker device and fee listener device is created. Otherwise, fee communication link is not established. In an implementation, data or information published by fee writer is provided to fee talker devices which communicates fee data or information through fee TSN 103 to fee listener devices.

[026] The listener devices may then communicate fee data or information to fee reader. In an embodiment, fee end point devices may be communicatively coupled wife fee writer and fee reader devices. For example, fee end point devices may provide data (e.g., sensor data) to fee writer, which publishes or otherwise communicates fee data to fee talker devices as published data. The talker devices communicate fee published data to fee listener devices. The talker devices communicate fee data through one or more networked devices in fee TSN 103, such as routers and/or Ethernet switches. Further, the listener devices receive the data and communicates the data to the reader as received data. The reader may communicate the received data to the end point device, such as Human Machine interface (HMI)/UI, control system, and/or the actuators.

[027] In an embodiment, the plurality of TSN devices 105 refer to automation devices which are compliant to the TSN 103. As an example, the plurality of TSN devices 105 may be any automation devices such as, static control devices, programmable controllers, counters, switches and the like. A person skilled in the art would understand that the plurality of TSN devices 105 may include any other automation devices compliant to the TSN 103, not mentioned herein explicitly.

[028] Further, each of the plurality of intermediate TSN devices 101 is connected to respective a non-TSN device 107i, a non-TSN device 1072, .and a non-TSN device 107N (collectively referred as plurality of non-TSN device 107N). In an embodiment, the plurality of non-TSN devices 107 refer to automation devices which are not compliant to the TSN 103. As an example, the plurality' of non-TSN devices 107 may be any automation devices such as, static control devices, programmable controllers, counters, switches and the like. A person skilled in the art would understand that the plurality of non-TSN devices 107 may include any other automation devices compliant to the TSN 103, not mentioned herein explicitly. In one embodiment, the plurality of intermediate TSN devices 101 may include computing devices, such as a server. A person skilled in the art would understand that the scope of the present disclosure may encompass any other device as intermediate TSN device, not mentioned herein explicitly.

[029] Further, each of the plurality of intermediate TSN devices 101 includes an I/O interface 109, a memory 111 and a processor 113. FIG.lb illustrates a block diagram of an intermediate TSN device in accordance with an embodiment of the present disclosure. The I/O interface 109 may be configured to receive data from the plurality of non-TSN devices 107. The data received from the I/O interface 109 may be stored in the memory 111. In the present disclosure, processor 113 respective to each of the plurality of intermediate TSN devices 101 is configured to schedule data transmission for non-TSN devices over TSN. [030] To schedule the data transmission, initially, a plurality of TSN policies may be generated and stored in the plurality of non-TSN devices 107 using engineering data associated with respective plurality of non-TSN devices 107. In an embodiment, the plurality of TSN policies may be generated by a TSN engineering tool. The plurality of TSN policies is generated by identifying at least one of the talker devices and listener devices from the engineering data associated with the plurality of non-TSN devices 107. Further, communication traffic between the identified talker devices and the listeners devices is categorized to be one of a predefined communication type. In an embodiment, the predefined communication type may be categorised as isochronous, cyclic, events, network control, and configuration and diagnostic type.

[031] Thereupon, the plurality of TSN policies is generated based on the communication traffic between the talker devices and the listener devices and attributes associated with each communication type. In an embodiment, the plurality of TSN policies may be deployed in each of the plurality of intermediate TSN devices 101. Alternatively, the plurality⁷ of TSN policies may be stored in corresponding non-TSN devices and are fetched from the plurality of non-TSN devices on a request. In an embodiment, the plurality of TSN policies may be generated for the industrial system or only for a section of die industrial system. In real-time, whenever any non-TSN device of the plurality' of non-TSN devices 107 is connected to an intermediate TSN device of the plurality of intermediate TSN devices 101, the intermediate TSN device determines Media Access Control (MAC) address details for such non-TSN device by monitoring data traffic associated with the non-TSN device. In an embodiment, each of the plurality of intermediate TSN devices 101 is configured with a routing table which is used for storing MAC address of other intermediate TSN devices configured in the TSN 103 and non-TSN device connected to each of the other intermediate TSN devices.

[032] Further, the intermediate TSN device generates configuration data using a TSN policy associated with the non-TSN device. In an embodiment, the TSN policy associated with the non-TSN device is obtained from the plurality⁷ of TSN policies based on the MAC address details of the non-TSN device. Thereafter, the intermediate TSN device transmits the configuration data to the CUC associated with the TSN 103, which initiates configuration with the CNC of the TSN 103 based on the configuration data. In an embodiment, each of the plurality of intermediate TSN devices 101 may broadcast a request for determining MAC address for a target non-TSN device to other intermediate TSN devices configured in the TSN 103 when the destination MAC address is not found in the routing table. Further, in response to the broadcast request, each of the other intermediate TSN devices may check the MAC address of the target non TSN device and the one of the other intermediate TSN devices in respective routing table and provide to the requesting intermediate TSN device on identification.

[033] FIG.2a shows a detailed block diagram of an intermediate TSN device in sequence format for scheduling data transmission for non-TSN devices over TSN in accordance with an embodiment of the present disclosure.

[034] As shown in Fig.2a, an intermediate TSN device of the plurality of intermediate TSN devices 101 may include a policy generation module 201, a MAC address determination module 203, a configuration generation module 205 and a transmission module 207. The policy generation module 201 may be configured to generate the plurality of TSN policies associated with the plurality of non-TSN devices 107. The policy generation module 201 may generate the plurality⁷ of TSN policies using the engineering data associated with the plurality' of non-TSN devices 107. In an embodiment, the plurality of TSN policies associated with the plurality of non-TSN devices 107 may be deployed in each of the plurality intermediate TSN devices 101. Alternatively, the plurality of policies may be stored in corresponding plurality of non- TSN devices 107 and fetched from each of the non-TSN devices on specific request. FIG.2b illustrates a flowchart illustrating generation of TSN policies in accordance with an embodiment of the present disclosure.

[035] As shown in Fig.2b, at block 211 , the policy generation module 201 may identify the plurality of non-TSN devices 107 to be at least one of the talker devices and listener devices from the engineering data associated with the plurality of non-TSN devices 107. In an embodiment, talker devices are the devices which generate information and listener devices are devices which consume information. In an embodiment, the plurality of non-TSN devices 107 may be both talker device and the listener device.

[036] At block 213, after identification, the policy generation module 201 may categorize the communication traffic between the talker devices and the listeners devices to be one of a predefined communication type. In an embodiment, the predefined communication type may be isochronous, cyclic, events, network control, and configuration and diagnostic type. In an embodiment, each traffic type comprises one or more attributes. In an embodiment, the isochronous communication type requires each device to be synchronized with common time reference.

[037] Thus, in isochronous communication type devices synchronously sample inputs and apply outputs by exchanging data at define periodic rate. In cyclic communication type, devices sample inputs and apply outputs cyclically and data transmission period may or may not be same in every cycle. The events communication type is a message which is generated from the device or system when there is change in variables that requires attentions. Depending upon the change, the event may be single or flurry of messages. The network control is a control message. Typically, messages are low in volume but have critical delivery requirements. The configuration and diagnostics type are for transport of configuration and diagnostic data as configuration and firmware download. The data is typically sent over TCP/IP-based protocols.

[038] At block 215, the policy generation module 201 may generate the plurality of TSN policies based on the communication traffic between the talker devices and the listener devices and attributes associated with each communication type. In an embodiment, the attributes may be for example, periodicity', period, Time Synchronized Transmission, data delivery, tolerance to interference, max application data size, criticality and the like. In an embodiment, the plurality of TSN policies may include such as, device MAC address, device Role, mapping of source and destination MAC address, range of required update rate, message type, i.e. periodic/aperiodic, required number of non-TSN interface and the like. A person skilled in the art would understand that the TSN policies may also include any other details related to the non- TSN devices not mentioned herein explicitly.

[039] In an embodiment, the plurality of TSN policies may be updated from time to time based on the requirement. In an embodiment, sometimes, MAC address information associated with connected non-TSN device of the plurality of non-TSN devices 107 may not be available or not defined in the corresponding TSN policy. In such case, by default, communication for all such connected non-TSN device of the plurality of non- TSN devices 107 may be configured for best effort traffic. Later, tire intermediate TSN device may monitor destination MAC address and may obtain relevant information from the TSN policy.

[040] Whenever any non-TSN device of the plurality of non-TSN devices 107 is connected to an intermediate TSN device of the plurality of intermediate TSN devices 101, the MAC address determination module 203 may determine the Media Access Control (MAC) address details for the non-TSN device of the plurality of non-TSN devices 107. The MAC address determination module 203 determines the MAC address details by monitoring the data traffic associated with the non-TSN device. In an embodiment, the MAC address determination module 203 seeks the MAC address details of the non-TSN device in the corresponding routing table. In case, if the MAC address detail is found, the MAC address details of the relevant intermediate TSN device is retrieved. Alternatively, if the MAC address details are not found, the MAC address determination module 203 may initiate the broadcast request to all other neighbor intermediate TSN devices. On receiving the request, the MAC address determination module 203 of other intermediate TSN device may check the MAC address for the non-TSN device and provide to the requesting intermediate TSN device on identification.

[041] On determining the MAC address details for the non-TSN device, the configuration generation module 205 may generate the configuration data by using the TSN policy associated with the non-TSN device. On generating the configuration data, the transmission module 207 transmits the configuration data to the CUC of TSN 103. In an embodiment, the CUC initiate configuration with the CNC based on the configuration data for scheduling the data transmission. In an embodiment, the configuration is initiated with the CNC as per TSN IEEE 802.1Qcc standard.

[042] FIG.3a and Fig.3b illustrate an exemplary embodiment of discovering intermediate TSN devices in TSN in accordance with an embodiment of the present disclosure.

[043] Fig.3a illustrates the intermediate TSN device lOli, the intermediate TSN device 10 le connected with the TSN 103. A person skilled in the art would understand that Fig.3a and Fig.3b is an exemplary embodiment and the present disclosure may include plurality of intermediate TSN devices 101. In an embodiment, each of the plurality of intermediate TSN devices 101 may be connected with each other (not shown explicitly in Fig.3a and Fig.3b). Each of the plurality of intermediate TSN devices 101 stores MAC address of other intermediate TSN device configured in the TSN 103 and of the non-TSN devices connected to each of the other intermediate TSN device in a routing table. In an embodiment, the routing table is used for creating TSN traffic scheduling among the plurality of intermediate TSN devices 101. For example, the intermediate TSN device lOh may store the MAC address of the other intermediate TSN devices (lOh, 10 U). and corresponding non-TSN devices. In an instance, when any new intermediate TSN device is connected to the TSN 103, such intermediate new TSN device may broadcast a status to other intermediate TSN devices in the TSN 103.

[044] Subsequently, each of the other intermediate TSN devices establishes secure session with the new TSN intermediate device and reads device information and details of corresponding connected non-TSN devices. In an embodiment, when any new non- TSN device is connected to an intermediate TSN device of the plurality of intermediate TSN devices 101, the new non-TSN device may be configured as a network switch and operates on non-TSN mode i.e. best effort traffic transmission mode. Such new non-TSN device receives IP address and initiates communication with intended communication device. At Layer 2, the intermediate TSN device to which the new non-TSN device is connected, monitors the data traffic such as source and destination MAC address, data size, period transmission rate and the like. Further, the intermediate TSN device of the plurality of intermediate TSN devices 101 seeks MAC address of the new non-TSN device in corresponding routing table. In case, if MAC address is found, the MAC address details of the relevant intermediate TSN device is retrieved. Alternatively, if the MAC address details are not found, the intermediate TSN device broadcast the request to all other neighbor intermediate TSN devices.

[045] On receiving the request, the other intermediate TSN device checks the MAC address for the newly connected non-TSN device and provide to the requesting intermediate TSN device on identification. Further, each of the plurality of intermediate TSN devices 101 creates a unique two bytes alias address for corresponding non-TSN devices. Fig.3b illustrates an address format created by intermediate TSN devices. The unique two-byte alias address as shown in Fig.3b is used for wrapping and unwrapping of messages of the plurality of non-TSN devices 107. In an embodiment, the unique two bytes address helps to minimize packet size of the plurality of non-TSN devices 107 during wrapping and un-wrapping phase.

[046] FIG.4 illustrates a flowchart for scheduling data transmission for non-TSN devices over TSN in accordance with an embodiment of the present disclosure.

At block 401, the intermediate TSN device of the plurality of intermediate TSN devices 101 determine Media Access Control (MAC) address details for the non-TSN device of the plurality of non-TSN devices 107. The MAC address details are determined by monitoring data traffic associated with the non-TSN device.

[047] At block 403, the intermediate TSN device of the plurality of intermediate TSN devices 101 generate configuration data using the TSN policy associated with the non- TSN device. The TSN policy associated with the non-TSN device is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device. In an embodiment, the plurality of TSN policies is generated based on the communication traffic data between the talker devices and the associated listener devices and attributes associated with each communication type.

[048] At block 405, the intermediate TSN device of the plurality⁷ of intermediate TSN devices 101 transmits the configuration data to the CUC. The CUC initiate configuration with the CNC based on the configuration data for scheduling the data transmission.

[049] In an embodiment, the present disclosure facilitates data scheduling for non-TSN devices over TSN 103.

[050] In an embodiment, the use of intermediate TSN devices in place of vendor-specific TSN gateway helps to minimize the configuration complexity and workflows based on connected industrial device or application.

[051] An embodiment of the present disclosure provides a seamless dynamic configuration of intermediate TSN devices, without complex engineering. One-time TSN policies are generated based on engineering data for all intermediate TSN devices which along with devices information of the connected non-TSN devices provide workflow for automated seamless configuration.

[052] An embodiment of the present disclosure allows other intermediate TSN devices to discover neighboring intermediate TSN devices and its connected non TSN devices. In case of any device update, maintenance, and replacement, the present invention minimizes the configuration effort.

[053] An embodiment of the present disclosure provides auto provisioning which enables auto generation of TSN specific configuration based on non TSN device communication. Based on communication traffic, the intermediate TSN devices auto updates TSN related configuration without any manual innervation.

[054] This written description uses examples to describe the subject matter herein, including the best mode, and also to enable any person skilled in the art to make and use the subject matter. The patentable scope of the subject matter is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.

REFERRAL NUMERALS

Claims

We claim:

1. An intermediate Time Sensitive Networking (TSN) device (101) configured in a TSN (103) for scheduling data transmission for non-TSN devices over the TSN (103), the TSN (103) comprising a Centralized User Configuration (CUC) and a Centralized Network Configuration (CNC) for scheduling data transmission, and one or more end point devices, wherein the one or more end point devices comprise talker devices and associated listener devices, wherein the intermediate TSN device (101) is connected between at least one of a plurality of TSN devices (105) and non-TSN devices (107) with a plurality of non-TSN devices (107), wherein the intermediate TSN device (101) comprises a processor (113) and a memory (111) communicatively coupled to the processor (113), wherein the memory (111) stores processor instructions, which, on execution, causes the processor (113) to:

determine Media Access Control (MAC) address details for a non-TSN device of the plurality of non-TSN devices (107) by monitoring data traffic associated with the non-TSN device;

generate configuration data using a TSN policy associated with the non-TSN device, wherein the TSN policy associated with the non-TSN device is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device, wherein the plurality of TSN policies is generated based on communication traffic data between the talker devices and the associated listener devices and attributes associated with each communication type; and

transmit the configuration data to the CUC, wherein the CUC initiate configuration with the CNC based on the configuration data for scheduling the data transmission.

2. The intermediate TSN device (101) as claimed in claim 1, wherein the plurality of TSN policies is generated using engineering data associated with the plurality of non-TSN devices (107) by:

identifying the plurality of non-TSN devices (107) to be at least one of the talker devices and listener devices;

categorising communication traffic between the talker devices and the listeners devices to be one of a predefined communication type; and

generating the plurality of TSN policies based on the communication traffic between the talker devices and the listener devices and attributes associated with each communication type.

3. The intermediate TSN device (101) as claimed in claim 1, wherein the plurality of TSN policies is deployed in the intermediate TSN device (101).

4. The intermediate TSN device (101) as claimed in claim 1, wherein the plurality of TSN policies are fetched from the plurality of non-TSN devices (107) on a request.

5. The intermediate TSN device (101) as claimed in claim 1 stores MAC address of other intermediate TSN devices configured in the TSN and non-TSN device connected to each of the other intermediate TSN devices in a routing table configured in the intermediate TSN device (101), wherein the intermediate TSN device (101) receives MAC address of other intermediate TSN devices and the non-TSN device connected to each of the other intermediate TSN devices in response to a broadcast message sent by the intermediate TSN device (101) when connected to the TSN (103).

6. The intermediate TSN device (101) as claimed in claim 5 broadcasts a request for determining MAC address for a target non-TSN device to other intermediate TSN devices configured in the TSN (103) when the destination MAC address is not found in the routing table, and receives the MAC address from one of the other intermediate TSN devices, wherein each of the other intermediate TSN devices check MAC address of the target non TSN device and the one of the other intermediate TSN devices provides the MAC address to the intermediate TSN device (101) on identification.

7. An industrial control system comprising the intermediate TSN device (101) for scheduling data transmission for non-TSN devices over the TSN (103) as claimed in claim 1.

8. A method of enabling real-time data communication over Time Sensitive Networking (TSN) (103) for non-TSN devices, wherein the TSN (103) comprises a Centralized User Configuration (CUC) and a Centralized Network Configuration (CNC) for scheduling data transmission, and one or more end point devices, wherein the one or more end point devices comprises talker devices and associated listener devices, wherein to enable the data communication for non-TSN devices, the TSN comprises a plurality of intermediate TSN devices (101) connected between at least one of a plurality of TSN devices (105) and non- TSN devices (107) with a plurality ofnon-TSN devices (107), the method is performed by each of the plurality of intermediate TSN devices (101), the method comprising: determining Media Access Control (MAC) address details for a non-TSN device of the plurality of non-TSN devices (107) by monitoring data traffic associated with the non-TSN device;

generating configuration data using a TSN policy associated with the non-TSN device, wherein the TSN policy is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device, wherein the plurality of TSN policies is generated based on communication traffic data between the talker devices and associated listener devices and attributes associated with each communication type; and

transmitting the configuration data to the CUC, wherein the CUC initiate configuration with the CNC based on the configuration data for scheduling the data transmission.

9. The method as claimed in claim 8, wherein the plurality of TSN policies is generated using engineering data associated with the plurality' of non-TSN devices (107) by:

identifying the plurality of non-TSN devices ( 107) to be at least one of the talker devices and listener devices;

generating the plurality of TSN policies based on the communication traffic between tire talker devices and the listener devices and attributes associated with each communication type.

10. The method as claimed in claim 8, wherein the plurality of TSN policies is deployed in each of the plurality of intermediate TSN devices (101).

11. The method as claimed in claim 8, wherein the plurality of TSN policies are fetched from the plurality of non-TSN devices (107) on a request.

12. The method as claimed in claim 8 comprising storing MAC address of other intermediate TSN devices configured in the TSN (103) and non-TSN device connected to each of the other intermediate TSN devices in a routing table configured in each of the plurality of intermediate TSN devices (101), wherein an intermediate TSN device (101) receives MAC address of other intermediate TSN devices and the non-TSN device connected to each of the other intermediate TSN devices in response to a broadcast request sent by the intermediate TSN device (101) when connected to the TSN (103).

13. The method as claimed in claim 12 comprising broadcasting the request for determining MAC address for a target non-TSN device to other intermediate TSN devices configured in the TSN (103), when the MAC address is not found in the routing table, and receives the MAC address from one of the other intermediate TSN devices, wherein each of the other intermediate TSN devices check MAC address of the target non TSN device and the one of the other intermediate TSN devices provides the MAC address to the intermediate TSN device (101) requesting the MAC address on identification.

14. A Time Sensitive Networking (TSN) (103) comprising a Centralized User Configuration (CUC) and a Centralized Network Configuration (CNC) for scheduling data transmission, and one or more end point devices, wherein the one or more end point devices comprise talker devices and associated listener devices, wherein the TSN (103) comprises a plurality of intermediate TSN devices (101) for enabling the data communication over TSN (103) for non- TSN devices, the plurality of intermediate TSN devices (101) are connected between at least one of a plurality of TSN devices(105) and non-TSN devices (107) with a plurality of non- TSN devices (107), wherein each of tire plurality of intermediate TSN devices (101) is configured to: determine Media Access Control (MAC) address details for a non-TSN device of the plurality of non-TSN devices (107) by monitoring data traffic associated with the non-TSN device;

generate configuration data using a TSN policy associated with the non-TSN device, wherein the TSN policy is obtained from a plurality of TSN policies based on the MAC address details of the non-TSN device, wherein the plurality of TSN policies is generated based on communication traffic data between the talker devices and associated listener devices and attributes associated with each communication type; and