WO2020081062A1

WO2020081062A1 - Wireless network support for ieee tsn based industrial automation

Info

Publication number: WO2020081062A1
Application number: PCT/US2018/056053
Authority: WO
Inventors: Vinh Van Phan; Matti Laitila; Ling Yu; Vladimir Vukadinovic; Kari Niemela; Rakash SIVASIVA GANESAN; Devaki Chandramouli; Troels Kolding
Original assignee: Nokia Technologies Oy; Nokia Usa Inc.
Priority date: 2018-10-16
Filing date: 2018-10-16
Publication date: 2020-04-23

Abstract

A UE, in a wireless communications system, indicates a capability of serving a TSN toward the wireless communications system. The UE receives control information for the TSN from a switch in the TSN and coupled to the UE. The UE sends the received control information for the TSN toward the wireless communication system. A network element in the wireless communication system receives control information, targeted to a CNC entity in the TSN, of a switch from a UE serving the TSN system via the switch. The network element updates context of the UE and the switch and sends the updated context toward the CNC entity. The network element receives control information of the switch from the CNC entity, updates context, determines QOS and scheduling assistance information based on the control information, and sends to elements in the wireless communication network. The network element sends the updated context to the switch.

Description

Wireless Network Support for IEEE TSN Based Industrial Automation

TECHNICAL FIELD

[0001] This invention relates generally to industrial automation (IA) and other time-sensitive networking (TSN) applications and, more specifically, relates to providing wireless network support for such IA.

BACKGROUND

[0002] This section is intended to provide a background or context to the invention disclosed below. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived, implemented or described.

Therefore, unless otherwise explicitly indicated herein, what is described in this section is not prior art to the description in this application and is not admitted to be prior art by inclusion in this section. Abbreviations that may be found in the specification and/or the drawing figures are defined below, at the beginning of the detailed description section.

[0003] Time sensitive networking (TSN) is being standardized by IEEE 802.1 to provide industrial networks with deterministic delay to handle time sensitive traffic. Currently, wired links are assumed for connecting the sensors and controllers. Moving from wired to wireless sensors and actuators provide advantages, such as mobility, scalability, low cost maintenance, and the like. To connect the wireless devices to a TSN network, wireless transmission technologies such as the ones defined in 3 GPP are necessary. While description herein centers on 3 GPP networks, these networks could be generalized to any wireless communication system.

[0004] A key feature necessary to achieve deterministic end-to-end (E2E) latency in a TSN network is by synchronizing all the network elements to a master clock in the system. In the conventional TSN network with wired links, this is achieved to a precision of fraction of a nanosecond. However, for wireless links, the maximum precision possible is limited to the sampling time, e.g., for 20 MHz bandwidth this corresponds to 32 nanoseconds. In order to achieve deterministic E2E (end-to-end) latency for a system with both a wireless

communications network and a TSN network, new mechanisms are needed. BRIEF SUMMARY

[0005] This section is intended to include examples and is not intended to be limiting.

[0006] An exemplary embodiment is a method. The method comprises indicating, by a user equipment in a wireless communications system, a capability of serving a time sensitive network. The indicating is performed by the user equipment toward the wireless

communications system. The method includes receiving, by the user equipment, control information for the time sensitive network from a switch in the time sensitive network and coupled to the user equipment. The method includes sending, by the user equipment, the received control information for the time sensitive network toward the wireless communication system.

[0007] An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is_. run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.

[0008] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer pro ram code are configured to, with the one or more processors, cause the apparatus to perform at least the following: indicating, by a user equipment in a wireless communications system, a capability of serving a time sensitive network, the indicating performed by the user equipment toward the wireless communications system; receiving, by the user equipment, control information for the time sensitive network from a switch in the time sensitive network and coupled to the user equipment; and sending, by the user equipment, the received control information for the time sensitive network toward the wireless communication system.

[0009] An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code for indicating, by a user equipment in a wireless communications system, a capability of serving a time sensitive network, the indicating performed by the user equipment toward the wireless communications system; code for receiving, by the user equipment, control information for the time sensitive network from a switch in the time sensitive network and coupled to the user equipment; and code for sending, by the user equipment, the received control information for the time sensitive network toward the wireless communication system.

[0010] In another exemplary embodiment, an apparatus comprises: means for indicating, by a user equipment in a wireless communications system, a capability of serving a time sensitive network, the indicating performed by the user equipment toward the wireless communications system; means for receiving, by the user equipment, control information for the time sensitive network from a switch in the time sensitive network and coupled to the user equipment; and means for sending, by the user equipment, the received control information for the time sensitive network toward the wireless communication system.

[0011] In an exemplary embodiment, a method is disclosed that includes receiving, at a network element in a wireless communication system, control information of a switch from a user equipment serving the time sensitive network system via the switch and in the wireless communication system. The switch is in the time sensitive network system and the control information is targeted to a centralized network configuration entity in the time sensitive network system. The method includes updating by the network element context of the user equipment and the switch. The method includes sending by the network element the received control information including the updated context of the user equipment and the switch toward the centralized network configuration entity of the time sensitive network system.

[0012] An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.

[0013] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus to perform at least the following: receiving, at a network element in a wireless communication system, control information of a switch from a user equipment serving the time sensitive network system via the switch and in the wireless communication system, wherein the switch is in the time sensitive network system and the control information is targeted to a centralized network configuration entity in the time sensitive network system; updating by the network element context of the user equipment and the switch; and sending by the network element the received control information including the updated context of the user equipment and the switch toward the centralized network configuration entity of the time sensitive network system.

[0014] An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code for receiving, at a network element in a wireless communication system, control information of a switch from a user equipment serving the time sensitive network system via the switch and in the wireless communication system, wherein the switch is in the time sensitive network system and the control information is targeted to a centralized network configuration entity in the time sensitive network system; code for updating by the network element context of the user equipment and the switch; and code for sending by the network element the received control information including the updated context of the user equipment and the switch toward the centralized network configuration entity of the time sensitive network system.

[0015] In another exemplary embodiment, an apparatus comprises: means for receiving, at a network element in a wireless communication system, control information of a switch from a user equipment serving the time sensitive network system via the switch and in the wireless communication system, wherein the switch is in the time sensitive network system and the control information is targeted to a centralized network configuration entity in the time sensitive network system; updating by the network element context of the user equipment and the switch; and sending by the network element the received control information including the updated context of the user equipment and the switch toward the centralized network configuration entity of the time sensitive network system.

[0016] In an exemplary embodiment, a method is disclosed that includes receiving, at a network element in a wireless communication system, control information of a switch in a time sensitive network. The control information is received from a centralized network configuration entity of the time sensitive network. The method includes updating, by the network element, context of the switch and a corresponding user equipment serving the time sensitive network and in the wireless communication system. The method also includes determining by the network element a quality of service setting and scheduling assistance information concerning at least a communication session corresponding to the control information. The method further includes sending by the network element the quality of service setting and scheduling assistance information to at least one and up to all of the following elements in the wireless communication system: user equipment, a serving radio access network node, and a user plane function. The method includes sending by the network element the updated control context to the switch via the user equipment.

[0017] An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the co puter pro ram is run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.

[0018] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus to perform at least the following: receiving, at a network element in a wireless communication system, control information of a switch in a time sensitive network, the control information received from a centralized network configuration entity of the time sensitive network;

updating, by the network element, context of the switch and a corresponding user equipment serving the time sensitive network and in the wireless communication system; determining by the network element a quality of service setting and scheduling assistance information concerning at least a communication session corresponding to the control information; sending by the network element the quality of service setting and scheduling assistance information to at least one and up to all of the following elements in the wireless communication system: user equipment, a serving radio access network node, and a user plane function; and sending by the network element the updated control context to the switch via the user equipment.

[0019] An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code for receiving, at a network element in a wireless communication system, control information of a switch in a time sensitive network, the control information received from a centralized network configuration entity of the time sensitive network; code for updating, by the network element, context of the switch and a corresponding user equipment serving the time sensitive network and in the wireless communication system; code for determining by the network element a quality of service setting and scheduling assistance information concerning at least a communication session corresponding to the control information; code for sending by the network element the quality of service setting and scheduling assistance information to at least one and up to all of the following elements in the wireless communication system: user equipment, a serving radio access network node, and a user plane function; and code for sending by the network element the updated control context to the switch via the user equipment.

[0020] In another exemplary embodiment, an apparatus comprises: means for receiving, at a network element in a wireless communication system, control information of a switch in a time sensitive network, the control information received from a centralized network configuration entity of the time sensitive network; means for updating, by the network element, context of the switch and a corresponding user equipment serving the time sensitive network and in the wireless communication system; means for determining by the network element a quality of service setting and scheduling assistance information concerning at least a communication session corresponding to the control information; means for sending by the network element the quality of service setting and scheduling assistance information to at least one and up to all of the following elements in the wireless communication system: user equipment, a serving radio access network node, and a user plane function; and means for sending by the network element the updated control context to the switch via the user equipment.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In the attached Drawing Figures:

[0022] FIG. 1A is a schematic representation of a motion control system;

[0023] FIG. IB is block diagram of how the motion control system of FIG. 1 A might be integrated into a system with both a cellular wireless network and a TSN network;

[0024] FIG. 2 is a table illustrating typical characteristics of motion control systems for three major applications; [0025] FIG. 3 illustrates communication paths for isochronous control cycles within factory units;

[0026] FIG 3 A is a diagram of a 5G LAN private Ethernet network for integrating a wireless network and a TSN network;

[0027] FIG 3B is a diagram of another system for integrating a wireless network and a TSN network;

[0028] FIG 3C is a diagram of another system for integrating a wireless network and a TSN network, in accordance with an exemplary embodiment;

[0029] FIGS. 4A and 4B are block diagrams of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced, where FIG. 4B illustrates possible internal details certain ones of the entities in FIG. 4A;

[0030] FIG. 5 is a block diagram illustrating an enhanced C-plane with TSN-support NF and UE procedures carrying TSN-C signaling, in accordance with an exemplary embodiment;

[0031] FIG. 6 is a logic flow diagram according to some embodiments for wireless network support for IEEE TSN based industrial automation, performed by a TSN-serving UE;

[0032] FIG. 7 is a logic flow diagram according to some embodiments for wireless network support for IEEE TSN based industrial automation, performed by a TSN-support NF and illustrates TSN-control (TSN-C) information being communicated to a CNC;

[0033] FIG. 8 is a logic flow diagram according to some embodiments for wireless network support for IEEE TSN based industrial automation, performed by a TSN-support NF and illustrates TSN-control (TSN-C) information being communicated from a CNC;

[0034] FIG. 9 is a signaling diagram of TSN-C signaling over a C-plane of a serving 5G network for a UE-side TSN switch, in accordance with an exemplary embodiment;

[0035] FIG. 10 is a signaling diagram of a PDU session set up upon activation of a UE-side TSN switch, in accordance with an exemplary embodiment;

[0036] FIG. 11 is a signaling diagram of QoS setting and scheduling assistance for a TSN-related PDU session, in accordance with an exemplary embodiment;

[0037] FIG. 12 illustrates physical topology for an example workflow and how TSN switches may be configured to serve a TSN flow;

[0038] FIG. 13 is an illustration of a time budget for a serving 5G network to dehver TSN UL and DL, in an exemplary embodiment; [0039] FIG. 14 is a block diagram of one possible and non-limiting exemplary system, similar to the system in FIG. 4A but implementing a TSN switch within the serving 5G network, in accordance with an exemplary embodiment; and

[0040] FIG. 15 is an illustration of a time budget for a serving 5G network to deliver TSN UL and DL of use of a virtual TSN switch, in an exemplary embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

[0041] The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:

[0042] 3 GPP third generation partnership project

[0043] 5G fifth generation

[0044] 5GN 5G network

[0045] 5GC 5G core network

[0046] AF application function

[0047] AMF access and mobility management function

[0048] a.k.a. also known as

[0049] AP Application

[0050] AS Access Stratum

[0051] BS base station

[0052] CN core network

[0053] CNC centralized network configuration (or configurator) [0054] CPF control plane function

[0055] C-plane control plane

[0056] CU central unit

[0057] CUC centralized user configuration (or configurator)

[0058] DL Downlink

[0059] DRB data radio bearer

[0060] DU distributed unit

[0061] E2E end-to-end

[0062] eNB (or eNodeB) evolved Node B (e.g., an LTE base station) [0063] gNB (or gNodeB) base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC

[0064] EN-DC E-UTRA-NR dual connectivity

[0065] en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC

[0066] Eth Ethernet

[0067] E-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access technology

[0068] gPTP generalized PTP

[0069] HFN hyper frame number

[0070] IA industrial automation or industrial automation and

control

[0071] IZF interface

[0072] info information

[0073] LAN local area network

[0074] LLDP Link Layer Discovery Protocol

[0075] LTE long term evolution

[0076] MAC medium access control (layer)

[0077] MBMS multimedia broadcast multicast service

[0078] MME mobility management entity

[0079] MN mobile network

[0080] MCE network control element

[0081] MD media dependent

[0082] MT mobile termination

[0083] NAS Non-Access Stratum

[0084] NETCONF Network Configuration Protocol

[0085] NF network function

[0086] ng or NG new generation

[0087] ng-eNB or NG-eNB new generation eNB

[0088] NIC network interface card [0089] NR new radio

[0090] N/W or NW network

[0091] PCF policy control function

[0092] PDCP packet data convergence protocol

[0093] PDU Protocol Data Unit

[0094] PHY physical layer

[0095] PTP Precision Timing Protocol

[0096] QCI Quality of Service (QoS) Class Identifier

[0097] QoS quality of service

[0098] RAN radio access network

[0099] RB Radio Bearer

[00100] Rel release

[00101] RLC radio link control

[00102] RRH remote radio head

[00103] RRC radio resource control

[00104] RU radio unit

[00105] Rx receiver

[00106] S/A sensor/actuator

[00107] SDAP service data adaptation protocol

[00108] SDU Service Data Unit

[00109] SFN system frame number

[00110] SGW serving gateway

[00111] SMF session management function

[00112] SNMP Simple Network Management Protocol

[00113] TR technical report

[00114] TS technical specification

[00115] TSN time sensitive networking or time sensitive network

[00116] TTI transmission time interval

[00117] Tx transmitter

[00118] UDM Unified Data Management

[00119] UDR Unified Data Repository [00120] UE user equipment (e g., a wireless, typically mobile device)

[00121] UL Uplink

[00122] UPF user plane function

[00123] U-plane user plane

[00124] URLLC ultra-reliable low latency communication

[00125] WG working group

[00126] The word“exemplary” is used herein to mean“serving as an example, instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.

[00127] The rest of this document is divided, for ease of reference, into different sections.

[00128] 1. Introduction

[00129] The exemplary embodiments herein may be targeted for, e.g., 5G support of time-sensitive operations including challenging industrial automation (LA) use cases such as motion control ones in which applications running in a number of devices belonging to the same IA system are strictly synchronized and controlled by a master or central server with high-precision timing in order to ensure correct operation of the belonging IA system. See, for instance, 3GPP TR 22.804,“Study on Communication for Automation in Vertical Domains,”

1.0.0, December 2017. E2E communications required for IA systems are considered as being highly time sensitive and need high reliability. In some challenging IA applications that rely on cyclic communications for essential control loops, E2E URLLC with extremely low packet delay jitter is needed to meet short cycle time requirements. See, e.g., 3GPP TR 38.913,“Study on Scenarios and Requirements for Next Generation Access Technologies,” 14.3.0, June 2017. The semantics and technical characteristics of motion-control use cases for example are illustrated in 3 GPP TR 22.804, as follows.

[00130] FIGS. IA and IB are used to provide an overview of how LA systems might be structured. FIG. 1 A is a modified version of a schematic representation of a motion control system, and corresponds to Figure 5.3.2.1-1 from 3GPP TR 22.804,“Study on Communication for Automation in Vertical Domains,” 1.0.0, December 2017. A motion control system (and corresponding cycle) 1 is illustrated. A motion controller 2 sets set points 4 and sends these through a motor drive 5 to actuators 6. The actuators 6 act 8 on those set points 4 in order to perform the processes 10. There is a sensing 12 by the sensors 14 to sense the actual values 15 and send these back to the motor drive 5, which sends get points 18 to the motion controller 2.

[00131] FIG. 1B is block diagram of how the motion control system 1 of FIG.

1 A might be integrated into a system with both a cellular wireless network 100 and a TSN network 101. This is a simple introduction, and these networks are described in more detail below. In the IA system 90, used in a location such as in a factory, of FIG. IB, the wireless network 100 comprises the RAN node 170, the UPF 38, and the UEs 110-1, 110-2, and 110-3, while the TSN network 101 comprises the TSN switch 39, UE-side switches 38, and the end stations 34. The IA system 90 also includes the controller 2, motor drives 5, and motors 1 . There are three UEs, UE1 110-1, UE2 110-2, and UE 3 110-3, connected via corresponding wireless links 111-1, 111-2, and 111-3 to the RAN node 170. EachlJE 110 has a corresponding UE side boundary TSN switch 38-1, 38-2, and 38-3, and end station 34-1, 34-2 or 34-3 and a corresponding motor drive 5-1, 5-1, or 5-3 connected to a corresponding motor 19-1, 19-2, or 19-3. This illustrates one example for integrated the motion control system 1 into the IA system 90.

[00132] FIG. 2 is a table illustrating typical characteristics of motion control systems for three major applications, and corresponds to Table 5.3.2.1-1 from 3GPP TR 22.804,“Study on Communication for Automation in Vertical Domains,” 1.0.0, December 2017. The table shows applications 20, number (#) of sensors/actuators 22, typical message size 24, cycle time T_cycte 26, and service area 28. Thus, the cycle time 26 for the cycle 1 can be quite short, as little as 0.5 milliseconds (ms).

[00133] 1.1 Introduction from 3 GPP TS 22.261

[00134] Further details of the motion control use cases are described in 3 GPP TS 22.261,“Service requirements for the 5G system; Stage 1,” 16.3.0, March 2018. These are described below and much of the text in this section comes from 3GPP TS 22.261.

[00135] In Annex D of 3GPP TS 22.261, considered to be informative, some critical-communication use cases are illustrated. Section D.1 concerns discrete automation - motion control. [00136] This section details that industrial factory automation requires communications for closed-loop control applications. Examples for such applications are motion control of robots, machine tools, as well as packaging and printing machines. All other discrete-automation applications are addressed in Annex D.2.

[00137] The corresponding industrial communication solutions are referred to as fieldbusses. The pertinent standard suite is IEC 61158. Note that clock synchronization is an integral part of fieldbusses used for motion control.

[00138] In motion control applications, a controller interacts with a large number of sensors and actuators (e.g., up to 100), which are integrated in a manufacturing unit. The resulting sensor/actuator density is often very high (up to 1 m^'3, i.e., one sensor per cubic meter). Many such manufacturing units may have to be supported within close proximity within a factory (e.g., up to 100 in automobile assembly line production).

[00139] In a closed-loop control application (see FIG. 1 A), the controller periodically submits instructions to a set of sensor/actuator devices, which return a response within a cycle time. The messages, referred to as telegrams, are typically small (^:¾ 56 bytes). The cycle time can be as low as 2 ms (or lower according to FIG. 2), setting stringent end-to-end latency constraints on telegram forwarding (1 ms). Additional constraints on isochronous telegram delivery add tight constraints on jitter (1 ps), and the communication service has also to be highly available (99,9999%).

[00140] Multi-robot cooperation is a case in closed-loop control where a group of robots collaborate to conduct an action, for example, symmetrical welding of a car body to minimize deformation. This requires isochronous operation between all robots. For multi-robot cooperation, the jitter (1 ps) is among the command messages of a control event to the group robots.

[00141] To meet the stringent requirements of closed-loop factory automation, the following considerations may have to be taken:

[00142] Limitation to short-range communications.

[00143] Use of direct device connection between the controller and actuators.

[00144] Allocation of licensed spectrum for closed-loop control operations. Licensed spectrum may further be used as a complement to unlicensed spectrum, e.g., to enhance reliability. [00145] Reservation of dedicated air-interface resources for each link.

[00146] Combination of multiple diversity techniques to approach the high reliability target within stringent end-to-end latency constraints such as frequency, antenna, and various forms of spatial diversity, e.g., via relaying.

[00147] - Utilizing OTA time synchronization to satisfy jitter constraints for isochronous operation.

[00148] A typical industrial closed-loop motion control application is based on individual control events. Each closed-loop control event consists of a downlink transaction followed by a synchronous uplink transaction, both of which are executed within a cycle time. Control events within a manufacturing unit may have to occur isochronously. Factory automation considers application-layer transaction cycles between controller devices and sensor/actuator devices. Each transaction cycle consists of (1) a command sent by the controller to the sensor/actuator (downlink), (2) application-layer processing on the sensor/actuator device, and (3) a subsequent response by the sensor/actuator to the controller (uplink). Cycle time includes the entire transaction from the transmission of a command by the controller to the reception of a response by the controller. It includes all lower layer processes and latencies on the air interface as well the application-layer processing time on the sensor/actuator.

[00149] FIG. 3 illustrates communication paths for isochronous control cycles within factory units and corresponds to Figure D.l-1 from 3GPP TS 22.261,“Service requirements for the 5G system; Stage 1,” 16.3.0, March 2018. Figure D.l-l depicts how communication may occur in factory automation. In this use case, communication is confined to local controller-to-sensor/actuator interaction within each manufacturing unit. Repeaters may provide spatial diversity to enhance rehab ility. In a first step, the controller requests sensor data (or an actuator to conduct actuation) from the sensor/actuator (S/A) using isochronous requests. In a second step, the sensor (S/A) sends measurement information (or acknowledges actuation) to the controller.

[00150] In section D.1.1 , service area and connection density, it is indicated that the maximum service volume in motion control is currently set by hoisting solutions, i.e. cranes, and by the manipulation of large machine components, e.g., propeller blades of wind-energy generators. Cranes can be rather wide and quite high above the shop floor, even within a factory hall. In addition, they typically travel along an entire factory hall. An approximate dimension of the service area is 100 x 100 x 30 m. Note that production cells are commonly much smaller (< 10 x 10 x 3 m). There are typically about 10 motion-control connections in a production cell, which results in a connection density of up to 10⁵ km ² (i e , 100,000 per square kilometer).

[00151] This ends the description from 3GPP TS 22.261,“Service requirements for the 5G system; Stage 1,” 16.3.0, March 2018.

[00152] 1.2 Introduction for TSN

[00153] In current techniques for providing needed networking and

communication support for IA systems, IEEE 802.1 TSN has emerged as a popular technology. See, e.g., Cisco,“Time-Sensitive Networking: A Technical Introduction,” White Paper (2017).

[00154] This white paper states the following:

[00155] “In its simplest form, TSN is the IEEE 802.1Q defined standard technology to provide deterministic messaging on standard Ethernet. TSN technology is centrally managed and delivers guarantees of delivery and minimized jitter using time scheduling for those real-time applications that require determinism.

[00156] TSN is a Layer 2 technology. The IEEE 802.1 Q standards work at OSI Layer 2 TSN is an Ethernet standard, not an Internet Protocol standard. The forwarding decisions made by the TSN bridges use the Ethernet header contents, not the IP address. The payloads of the Ethernet frames can be anything and are not limited to Internet Protocol. This means that TSN can be used in any environment and can carry the payload of any industrial application.

[00157] TSN is a technology focused on time. TSN was developed to provide a way to make sure information can travel from point A to point B in a fixed and predictable amount of time.

[00158] • TSN flow: Term used to describe the time-critical

communication between end devices. Each flow has strict time requirements that the networking devices honor. Each TSN flow is uniquely identified by the network devices.

[00159] • End devices: These are the source and destinations of the TSN flows. The end devices are running an application that requires deterministic communication. These are also referred to as talkers and listeners.”

[00160] This ends the quotation from the white paper. [00161] Timing and synchronization in IEEE 802.1 TSN will be based on IEEE 802.lAS-Rev standard (see 5. IEEE P802.1AS-Rev/D7.3, Draft Standard to Local and Metropolitan Area Networks— Timing and Synchronization for Time-Sensitive Applications (August 2, 2018)) which will define a profile oflEEE 1588 PTP (see National Instruments, “Special Focus: Understanding the IEEE 1588 Precision Time Protocol,” (2005)) applicable in the context of IEEE Std 802.1 Q.

[00162] The National Instruments article states the following:

[00163] “The IEEE 1588 precision time protocol (PTP) provides a standard method to synchronize devices on a network with sub-microsecond precision. The protocol synchronizes slave clocks to a master clock ensuring that events and timestamps in all devices use the same time base. IEEE 1588 is optimized for user-administered, distributed systems; minimal use of network bandwidth; and low processing overhead.”

[00164] All of this illustrates that the synchronization between devices is very important.

[00165] Concerning TSN, TSN provides deterministic messaging for those real-time applications that require determinism. TSN makes sure that a packet of a uniquely identified TSN flow is delivered from one point to another point of the TSN in a fixed and predictable amount of time TSN therefore provides synchronized and guaranteed packet delivery with strictly constrained packet delay variation or, a.k.a., jitter, using time scheduling across TSN that can be centrally managed by a so-called Centralized Network Configuration (CNC) entity in practical centralized TSN systems. TSN is focused on time and the time synchronization across TSN is provided by using PTP. Note that the CNC is referred to as the Centralized Network Configuration and the CUC is referred to as Centralized User

Configuration in IEEE P801 1 Qcc/D2.3, Draft Standard for Local and Metropolitan Area Networks— Bridges and Bridged Networks (May 3, 2018). However, we will also refer to these as configurators (e.g., a Centralized User Configurator).

[00166] From a webpage for the Time-Sensitive Networking Task Group (see www.ieee802.org/l/pages/tsn.html), it states“The Time-Sensitive Networking Task Group is part of the IEEE 802.1 Working Group. The charter of the TSN TG is to provide deterministic services through IEEE 802 networks, i.e., guaranteed packet transport with bounded low latency, low packet delay variation, and low packet loss”. [00167] In summary, this states the following:“Time Sensitive Network is about guaranteed packet transport with bounded low latency, low packet delay variation, and low packet loss. The essence of TSN is to guarantee packet delivery within a bounded time window”.

[00168] Meanwhile, a 5G cellular network, however capable, has so far not been designed to provide synchronized packet delivery with deterministic QoS, especially in terms of: (i) delivering a packet considering the corresponding absolute time window; and (ii) delivering the packet in a synchronized manner between multiple UE(s), UPFs, RAN nodes and applications (apart from MBMS and/or broadcast). One principle behind current cellular networks is to provide a radio access connection to a mobile UE for various local and remote access applications and services. The radio access connection is provided and handled separately from transport- and application-level connections, following the model of separating between RAN and CN (core network), C-plane (control plane) and U-plane (user plane), AS (access stratum) and NAS (non-access stratum) on the C-plane coupled with flexible bearer service and QoS resolution. There is no strict timing synchronization of packet transmissions on the C-plane and U-plane. The radio transmissions between UE and BS of a serving RAN are synchronized for Tx/Rx radio operations on PHY and up to lower MAC for Ll transport blocks on the basis of predefined TTI for UL and DL separately. There is no strict timing for data transmissions on L2 and above, including upper MAC, RLC, PDCP and RRC on C-plane, except for timer operations guarding expected Tx/Rx events which are on the order of tens of milliseconds. NAS level signaling and timer operation between UE and CN for C-plane may adopt some system timing resolved using, e.g., SFN and HFN, as in LTE for instance. In other words, the packet transmission and delivery in cellular networks so far are asynchronous.

[00169] Thus, using a cellular network to provide radio connectivity for TSN end-points should consider how to leverage non-strict or unspecified synchro nicity or timing of current cellular packet access for the strictly synchronized and deterministic messaging of TSN.

[00170] There are alternative solutions to the problem of having 5G support for TSN. The following option, referred to as option B, has been investigated somewhat extensively. Turn to FIG. 3A, which is a diagram of a 5G LAN private Ethernet network 300. These might be implemented in hospitals, offices, ports, or factories. The 5G LAN private Ethernet network 300 comprises a 5G network 301 and a TSN network 302 The 5G LAN private Ethernet network 300 allows full integration of 5G in an industrial Ethernet network, and the collapsed 5G user plane in the TSN network 302, which requires every handover may involve a PDU session anchor relocation. There are three 5G access points (APs) 310 (with corresponding UPFs) and multiple UEs 320 in the 5G network 301. The TSN network 302 comprises multiple elements 330, such as robots, cranes, or thermometers, which may contain some of the elements from FIG. 1 A for instance, and also TSN bridges 350-1, 350-2, and 350-3. The 5G network 301 and TSN network 302 are fully integrated and both networks are managed together.

[00171] Based on this architecture option, a current approach is to encapsulate interworking functions at the edges to compensate for 3GPP internal jitter/misalignment as well as to translate external requirements (e.g., from TSN flows as well as from TSN system, e.g., the Centralized Network Configuration or CNC entity) to 3 GPP compliant ones. Another example of a possible system is illustrated in FIG. 3B. This illustrates a TSN end station A that is connected to an Ethernet (Eth) network interface card (NIC) in a UE, which also contains a TSN-MT (TSN-mobile termination) translator client and also the MT. The MT and UE are connected through a Uu interface to the NG-RAN node, which is connected via the N3 interface to the UPF and via the N2 interface to the AMF. The AMF is connected via the N11 interface to the SMF and via the N8 interface to an UDM/UDR. The SMF is connected via the N7 interface to the PCF and via the N4 interface to the UPF. The PCF is connected via the N5 interface to the TSN-MN translator in the TSN network side. The UPF is connected via the N6 interface to the TSN-MN translator. The TSN-MN translator comprises an AF :TSN translator for the control plane (CP) and a PDNtTSN translator for the user plane (UP). The AF:TSN translator is connected to the TSN CNC, and the PDN:TSN translator is connected to the TSN bridge, which is further connected to the TSN end station B. The TSN CNC is connected to the TSN CUC.

[00172] The 3GPP system, as well as the interworking functions, logically present themselves as a single TSN bridge and thus comply with existing management and E2E scheduling processes that are in use in today’s TSN networks. This logical TSN bridge also acts as a time-aware relay capable of time synchronization deli very using 802. IAS -Rev protocol. [00173] The techniques discussed in 3GPP SA2 for support of IA use cases and systems have been focused on the reliability aspect and not the time aspect, which is essential to TSN.

[00174] 2. Overview of exemplary systems

[00175] This section has an overview of exemplary systems suitable for implementing exemplary embodiments.

[00176] An exemplary embodiment provides a method for 5G to support TSN or, that is, using 5G to provide radio connectivity for TSN end-points. One exemplary motivation is to minimize changes to the aforementioned principle of current cellular networks in general while supporting TSN. Hence, an exemplary embodiment is, in principle, based on the architecture option illustrated in FIG. 3C. This option is referred to as option A. There is, of course, option B, as previously described.

[00177] The industrial factory 385 includes the LA system 90, which includes a serving 5G system 100 and a TSN system 101. The IA system 90 also includes network security 360 and industrial process controllers 302-1 and 302-2. The TSN network 101 includes elements 330-1 (e.g., a robot), 330-2 (e.g., a robot), 330-3 (e.g., a motor drive), and 330-4 (e.g., a camera), TSN bridges 350-1, 350-2, and 350-3, and sensors and actuators 6, 14. The serving 5G system 100, shown as 5G system (5GS), includes UEs 110-1 and 110-2, a RAN node 170 with base stations (e.g., gNBs), two UPFs 38 (UPF 38-1 and UPF 38-2), and one or more CPFs 380 (e.g., implemented by one or more of AMF, SMF, PCF, and/or AF) 380. Note that a TSN bridge and a TSN switch may be considered to be the same for the purposes of this disclosure. The interfaces Uu, N2, N3, N4, N6, and N9 are illustrated. The element 330-4 is an end station 34.

[00178] This architecture option A is a logically separated deployment, and has an industrial network including logically separated 5G system 100. The 5G system 100 is inside the industrial network (e.g., IA system 90), and the two systems are logically separated and each system can be managed autonomously.

[00179] For consistency it is assumed that UE 110-1 in FIG. 3C is equipped with an integrated TSN bridge 350 and a TSN end-station 34 is connected to the UE 110 via the TSN bridge as shown with the UE 110-2.

[00180] It is recognized that support of TSN imposes certain synchronicity and determinism on the serving 5G network 100. The serving 5G network 100, however, should be able to facilitate TSN data transmissions on the basis of individual TSN flows according to corresponding deterministic timing boundaries, as scheduled for individual TSN flows.

[00181] Exemplary embodiments herein aim for one or more of the following principles:

[00182] 1) Having a clear functional split between different domains: User-,

TSN Ethernet- and 5G System-domains;

[00183] 2) Providing robust adaptation to all the architecture models of TSN, as identified, e.g., in a IEEE 802.1Qcc specification;

[00184] 3) Providing full control in providing required synchronicity and determinism within the 5G domain, e.g., via an enhanced QoS framework of 5G, for serving individual TSN flows;

[00185] 4) Providing flexibility in redundancy and seamless mobility for a serving TSN;

[00186] 5) Reducing requirements for determinism within 5G domain, e.g., as much as possible.

[00187] How these principles are achieved is described in more detail below.

[00188] Turning to FIGS. 4A and 4B, these are block diagrams of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced, where FIG. 4B illustrates possible internal details of the entities in FIG. 4 A. In FIG. 4 A, the cellular wireless network 100 (referred to also as a serving 5G network below) interfaces with a TSN network 101 in the LA system 90, which might be used for instance in a factory. The architecture option A introduced above is referred to and illustrated in FIG. 4A as "5G as TSN link" structure 500.

[00189] The TSN network 101 comprises a CUC 30, a CNC 32, a TSN switch 39, two end stations 34-1 and 34-2, a UE side boundary TSN switch 36 (also referred to as a UE side TSN switch herein), and a UPF side boundary TSN switch 37 (also referred to as a UPF sign TSN switch herein). The UE side boundary TSN switch 36 is connected to the TSN end station 34-1 (in the TSN system 101) via a link 40, which is typically a non-wireless link such as an Ethernet cable, although optical fiber or other links might be used. Similarly, the UPF side boundary TSN switch 37 is connected to the TSN switch 39 (in the TSN system 101) via a link 41, which is typically a non- wireless link such as an Ethernet cable, although optical fiber or other links might be used. The following interfaces are used: ES-C between the CUC 30 and the end stations 34-1 and 34-2; and TSN-C between the CNC 32 and the UE side boundary TSN switch 36, the UPF side boundary TSN switch 37, and the TSN switch 39. The UE side boundary TSN switch 36 is connected to the UE 110 through a link 42, and the UPF 38 is connected to the UPF side boundary TSN switch 37 via a link 44.

[00190] The cellular wireless network 100 in this example has an extended 5G boundary 105 in supporting TSN. The cellular wireless network 100 comprises a UE 110, a RAN node 170, a UPF 38, an AMF 40, an SMF 42, a PCF 44 and a TSN-support network function (NF) 150. At least the TSN support NF 150 is implemented by a network control element (NCE) 190. The UPF 38 is implemented in a network element (NE) 190’. The NCE 190 is shown as also implementing some or all of the AMF and/or the SMF and/or the PCF. The following interfaces are illustrated: Nl between the AMF 40 and the UE 1 10; N2 between the AMF 40 and the RAN node 170; N3 between the RAN node 170 and the UPF 38; N6 between the UPF 38 and the UPF side boundary TSN switch 37; N4 between the UPF 38 and the SMF 42; Nl 1 between the AMF 40 and the SMF 42; and N7 between the SMF 42 and the PCF 44. There is also an N5 interface between the TSN support NF 150 and the CNC 32.

[00191] FIG. 4B shows isolated elements from FIG. 4A. In FIG. 4B, the user equipment (UE) 110, radio access network (RAN) node 170, and network control element(s) 190 are illustrated. In FIG. 4B, a user equipment (UE) 110 is in wireless communication with and part of the cellular wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a TSN module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways. The TSN module 140 maybe implemented in hardware as TSN module 140-1, such as being implemented as part of the one or more processors 120. The TSN module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the TSN module 140 maybe implemented as TSN module 140-2, which is implemented as computer program code 123 and is executed by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111

[00192] The RAN node 170 is a base station that provides access by wireless devices such as the UE 110 to the wireless network 100. The RAN node 170 maybe, for instance, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (e.g., the network control element(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the FI interface connected with the gNB-DU. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface 1 8 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of an RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station

[00193] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153 The CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown. The one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein.

[00194] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, e.g., an Xn interface for 5G, an XI interface for LTE, or other suitable interface for other standards.

[00195] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like.

[00196] The wireless network 100 may include a network control element or elements NCE(s) 190 or network elements) NE(s) 190’ that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management function(s) (AMF(S)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity)/SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network control element(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to the network control element (NCE) 190. The link 131 maybe implemented as, e.g., anNG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The NCE 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The NCE 190 includes a TSN support NF 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The TSN support NF 150 may be implemented in hardware as TSN support NF 150-1, such as being implemented as part of the one or more processors 175. The TSN support NF 150-1 maybe implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the TSN support NF 150 may be implemented as TSN support NF 150-2, which is implemented as computer program code 173 and is executed by the one or more processors 175. In a further example, the UPF 38 may be implemented by an NE 190’ and implemented as UPF 38-1 as hardware (e.g , in the one or more processors 175 or other circuitry) or as UPF 38-2 as computer program code 171 that is executed by the one or more processors 175. The one or more memories 171 and the computer program code 173 are therefore configured, with the one or more processors 175, to cause the NCE 190 to perform the operations described herein.

[00197] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.

[00198] The computer readable memories 125, 155, and 171 maybe of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 maybe means for performing storage functions. The processors 120, 152, and 175 maybe of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 maybe means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.

[00199] The structure in FIGS. 4A and 4B is based on an interworking model between TSN and 5G cellular networks, in which the serving 5G cellular network provides a smart radio access connection for a TSN transport link between a UE-side TSN switch 36 and a UPF-side TSN switch 37 as shown in FIG. 4 A, rather than integrated functions of a TSN bridge towards a TSN end-station or end-point via a UE 110. This structure, therefore, is referred to as the“5G as TSN link” option (also,“5G as TSN bridge” structure 500), as opposed to the“5G as TSN bridge” option described above (e.g., as option B).

[00200] In the“5G as TSN link” structure 500, the following functionality may be implemented.

[00201] 1 ) The UE-side boundary TSN switch 36 is responsible for the last- stage

TSN timing towards the TSN end-station 34-1 (e.g., an application within a host), whereas the UPF-side boundary TSN switch 37 is taking care of the TSN timing towards TSN in the network/application side.

[00202] 2) The serving 5G network 100 has control over at least the UE-side boundary TSN switch 36 and optionally the UPF-side boundary TSN switch 37, along with setting the propagation delays for the connection between the two boundary switches 36, 37 In general, it is assumed that the serving 5G network 100 is connected to the UPF side boundary TSN switch(es) 37 of individual TSN(s) being served. The serving 5G network 100 may optionally have one or more additional TSN switches (see FIG. 14) in between the two boundary switches 36, 37 so as to decompose the connection between the two boundary switches into more than one more controllable link if needed. These additional TSN switches are in between the two boundary switches 36, 37 and within the extended 5 G boundary 105 and under control of 5G network 100, whereas TSN switch 39 is native to TSN network 101, i.e., fully controlled by TSN network 101 and not 5G network 100. Hence, this kind of additional TSN switch is more like the UE-side TSN switch 36 from 5G network control perspective. However, there may be differences between this kind of TSN switch and the UE-side TSN switch 36, from 5G network access and connectivity perspectives. In general, the serving 5G network 100 may use TSN switches as a means to communicate and get scheduled times from the TSN controller (CNC 33). It is noted that the switch is a universal element of

communication networks. The serving 5G network domain with such TSN switch or switches is referred to as an extended 5G boundary 105. As described previously, additional TSN switches may be used between the two boundary switches 36, 37 and under control of 5G network 100, as clarified above. Note also that it is optional to have UPF side boundary TSN switch 37 under control of 5G network 100. Upon activation of a UE-side TSN switch 36 or a TSN switch in between the two boundary switches 36, 37 under control of the serving 5G network 100, the serving 5G network 100 may provide a smart radio access connection for interconnecting the TSN switch to the corresponding TSN system via a corresponding UPF-side boundary TSN switch 37.

[00203] 3) The serving 5G network 100 may provide smart radio access services for transporting TSN data traffic between a UE-side boundary TSN switch 36 and a UPF-side boundary TSN switch 37 with QoS control as per an individual TSN flow or as per a class of TSN flows which have, e.g., the same E2E latency and reliability requirements. That is, the “5G as TSN link” may be dynamically adapted based on QoS requirements of individual TSN flows to be served by the 5G network 100. The“5G as TSN link” structure 500 assumes that UE-side devices including TSN end-station(s) 34, UE-side boundary TSN switch 36 and UE 110, irrespective of whether they are integrated or not, are on the same platform, i.e., associated to each other beforehand and moving together.

[00204] Certain exemplary embodiments herein focus on facilitating on-the-fly activation of the TSN-serving UE 110 to the serving 5G network 100 and the UE-side TSN switch 42 to the belonging TSN system 101 under control of the serving 5G network 100, which is a part of the“5G as TSN link”. The following main proposals are briefly described here and described in more detail below.

[00205] FIG. 5 is a block diagram illustrating an enhanced C-plane (control plane) with TSN-support NF 150 and UE 110 procedures carrying TSN-C signaling, in accordance with an exemplary embodiment. That is, an exemplary embodiment enhances UE signaling procedures on the C-plane for TSN serving UE 110, including carrying certain TSN-C signaling of the UE-side TSN switch 36 towards the herein-introduced TSN-support NF 150. TSN-C signaling refers to, e.g., TSN network configuration and management signaling between a TSN switch and CNC 32 of a TSN system 101. In current TSN systems, TSN-C signaling is implemented using, e.g., NETCONF and/or SNMP protocols for examples. In the instant examples, as the UE-side TSN switch 36 is considered as being under control of the serving 5G network 100, the TSN serving UE 110 is configured to transfer certain TSN-related network configuration and management signaling between the UE-side TSN switch 36 and the introduced TSN-support NF 150. Hence, there can be different options to implement TSN-C signaling between the UE-side TSN switch and the TSN-support NF, e.g., either based on using existing protocols such as NETCONF and/or SNMP, or introducing TSN-C information objects for signaling TSN-C within the 5G domain. The UE procedures used for the TSN serving UE 110 to signal TSN-C related information towards the

TSN-support NF 150 maybe based on enhancing existing UE procedures, such as UE capability indication, UE assistance information, UE direct transfer of NAS signaling, UE connection establishment, and so forth, or introducing new UE procedures. As described above, the TSN-support NF may be implemented into one or more of existing AMF, SMF or PCF, for examples.

[00206] In the example of FIG. 5, the TSN-C plane for TSN-C signaling 510 is shown between the CNC 32 and the TSN support function 150, carried on the N5 interface. That is, the TSN-C signaling 510 is carried on the 5G system control plane (i.e. RRC and NAS signaling) to enable transmission of TSN-C/control plane signaling. The existing RRC and NAS signaling, consequently, may be extended to carry TSN-C messages or new RRC/NAS signaling message may be defined in order to carry TSN-C messages. If the NF 150 is distributed over the AMF 40, the SMF 42, and the PCF 44, as illustrated in FIG 5, the TSN-C plane and corresponding TSN-C signaling 510 operates also between the AMF 40, the SMF 42, and the PCF 44, on the corresponding Ni l and/or N7 interfaces (e.g , via the 5G system control plane ). The TSN-C plane and corresponding TSN-C signaling 510 also operates from the AMF 40 (or whichever element implements the TSN support function 150 and is configured to implement the TSN-C plane and corresponding TSN-C signaling 510) and the UE 110, on the Nl interface, and between the UE 110 and the UE side boundary TSN switch 36, e.g., on the 5G system control plane.

[00207] The TSN-support NF 150 is expected to provide one or more of the following exemplary functions:

[00208] 1) Maintaining contexts of TSN-serving UEs 110 and UE-side TSN switches 36 as well as UPF-side TSN switches 37 per a corresponding TSN system 101 being served; and/or

[00209] 2) Relaying or communicating TSN related network configuration and management signaling (e.g., TSN-C messages via the TSN-C plane and corresponding TSN-C signaling 510) between individual TSN switches under control of the serving 5G network 100, e.g., at least UE-side TSN switches 36, and CNC 32 of the corresponding TSN system 101; and/or

[00210] 3) Triggering a U-plane connection setup including a PDU session for interconnecting a UE-side TSN switch 36 to corresponding UPF-side TSN switch(es) 37 and any other TSN switch(es) in between, upon activation of those TSN switch(es) under control of the serving 5G network 100 before serving an actual TSN flow, where the PDU session may be used for, e.g., TSN synchronization and management of at least the UE-side TSN switch 36 towards the corresponding UPF-side TSN switch 37 and TSN system 101 (e.g., exchanging LLDP or PTP messages); and/or

[00211] 4) Setting at least some of the capability constraints of individual

UE-side TSN switches and the propagation delays of individual TSN links associated with individual TSN switches under control of the serving 5G network, based on, e.g., provisioning and/or monitoring relevant QoS constraints the serving 5G network may provide or guarantee towards corresponding TSN serving UEs, and communicating those toward CNC as well as relevant NFs and network nodes of the serving 5G network; and/or

[00212] 5) Maintaining contexts of TSN flows per each TSN-serving UE 110 and UE-side TSN switch 36 (mapping between TSN flows and PDU sessions and RB services); and/or

[00213] 6) Configuring TSN switches under control of the serving 5G network

100 for individual TSN flows based upon TSN configurations, including scheduling information, received from the CNC 32 for individual TSN flows (e.g., including at least TSN parameters that are forwarded towards the serving 5G network(s) 100); and/or

[00214] 7) Determining, based on the scheduling information received from the

CNC 32 on individual TSN flows, QoS setting and scheduling assistance information for corresponding PDU sessions and RBs and indicating that to at least one of the TSN-serving UE 110, serving RAN node 170, and/or UPF 38.

[00215] The“5G as TSN link” structure 500 therefore introduces the UE-side TSN switch 36 per TSN-serving UE 110. Hence, the“5G as TSN link” structure 500 assumes that the TSN domain is able to accommodate as many TSN switches as the number of needed TSN-serving UEs. The TSN control overhead, i.e., due to TSN-C signaling concerning network configuration and management of UE-side TSN switches (but not TSN flows), is therefore scaled up with the number of needed TSN-serving UEs. On the other hand, having the UE-side TSN switch does not cause scalability issues to the serving 5G network 100, as the serving 5G network 100 needs to provide connections and services to all the needed

TSN-serving UEs 110 anyway. To leverage the scalability issue towards the TSN domain while taking control of at least UE-side TSN switches 36, the introduced TSN-supportNF 150 may be acting as a CNC proxy to all the TSN switches 36 in the extended 5G boundary, and is referred to as the secondary CNC. The CNC 32 of TSN is referred to as the primary CNC. The secondary CNC may feed the primary CNC 32 with all the needed information related to all TSN switches within the extended 5G boundary 105.

[00216] 3. Introduction to possible exemplary methods

[00217] FIGS. 6, 7, and 8 illustrate some embodiments from perspectives of the

TSN-serving UE 110 (FIG. 6) and the TSN-support NF 150 (FIGS. 7 and 8).

[00218] Turning to FIG. 6, this figure is a logic flow diagram according to some embodiments for wireless network support for IEEE TSN based industrial automation, performed by a TSN-serving UE. This figure also illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. In an example, the UE 110, under control of the TSN module 140 at least in part, performs the blocks in FIG. 6.

[00219] In block 610, the TSN-serving UE 110 performs the operation of indicating a TSN-serving UE capability to the 5G serving network 100. The TSN-serving UE 110 performs the operation of receiving (e.g., via the TSN-C signaling 510) TSN-C information from the UE-side TSN switch 36. The TSN-C information is targeted to the CNC. See block 620. For instance, the TSN-C from the UE side switch 36 to the UE 110 is more like the device internal interface especially configured for the integrated implementation of UE side switch 36 and UE 110. That is, the TSN-C information from UE-side TSN switch 36 may imply it is targeted to the CNC. Therefore, no explicit indication of targeting the CNC may be needed. Or another exemplary option for targeting the CNC is by having a destination address of the CNC in a packet.

[00220] In block 630, the TSN-serving UE 110 performs the operation of sending the received TSN-C information to the 5 G serving network 100, e.g., using RRC and NAS signaling on the C-plane of the serving 5G network. This is sent at least to the TSN support function 150 of the serving 5G network 100, for use by the serving 5G network 100 to manage control of a communication session in the wireless communication system for a TSN flow, and/or for use by the TSN system (e.g., CNC 32) to manage the TSN flow and/or the UE-side TSN switch 36 The TSN flow is between two end stations 34-1, 34-2 in the time sensitive network 101 and will pass through at least the switch (e.g., a UE-side TSN switch 36) and the UE 110 of the wireless communication system (e.g., the serving 5G network). From the perspective of the serving 5G network 100, the TSN-C between the CNC 32 and the UE-side TSN switch 35 may be used for a communication session set up to enable the TSN flow between the two end stations 36, 37, and this communication set up may be performed in part by the TSN-serving UE 110 in block 630. Furthermore, in a TSN network 101, the CNC 32 and a TSN switch such as switch 36 may exchange TSN C-plane signaling for, e.g., network topology discovery, capability information (e.g., delay characteristics), scheduling information (e.g., Tx&Rx window), and the like. The TSN-C and the corresponding management of the TSN flow in block 630 will cover all of those signaling instances in the TSN network 101 between the CNC and TSN switches such as switch 36. That is, the TSN-serving UE 110 will pass this signaling between the CNC 32 and the switch 36.

[00221] FIGS. 7 and 8 concern a TSN support function 150 and its

communications with the TSN network 101 via, e.g., the CNC 32 (e.g., and the TSN-C plane and corresponding TSN-C signaling 510). FIG. 7 is directed to control information going toward the TSN network 101, and FIG. 8 is directed to control information coming from the TSN network 101.

[00222] FIG. 7 is a logic flow diagram according to some embodiments for wireless network support for IEEE TSN based industrial automation, performed by a

TSN-support NF and illustrates TSN-control (TSN-C) information being communicated to a CNC. This figure also illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. In this example, the TSN-support NF 150, as implemented by the NCE 190, performs the blocks in FIG. 7.

[00223] The TSN support function 150 in block 710 performs the operation of receiving TSN-C information of a UE-side TSN switch 36 from a TSN serving UE 110. The TSN-C information is targeted to a CNC. In block 720, the TSN support function 150 performs the operation of updating context of the TSN-serving UE 110 and UE-side TSN switch 36. The context is related to the TSN network 101 such as the timing, the scheduling information (e.g., Tx and Rx window) and the like, The TSN support function 150 sends in block 730 the TSN-C information including the updated context of the UE-side TSN switch 36 to a CNC 32 of the corresponding TSN system 101. The sending uses the TSN-C signaling 510 using, e.g., theN5 interface on a C-plane of the serving 5G network 100 (e.g., see FIG. 5). The TSN-C information is for use by the CNC 32 to manage and control the UE-side TSN switch 36 and the TSN flow between two end stations 34-1 , 34-2 in the time sensitive network 101. The TSN flow will pass through at least the switch (a UE-side TSN switch 6) and the UE 110 of the serving 5G network.

[00224] FIG. 8 is a logic flow diagram according to some embodiments for wireless network support for IEEE TSN based industrial automation, performed by a

TSN-support NF and illustrates TSN-control (TSN-C) information being communicated from a CNC. This figure also illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. In this example, the TSN-support NF 150, as implemented by the NCE 190, performs the blocks in FIG. 8.

[00225] The TSN support function 150 in block 810 performs the operation of receiving TSN-C information targeted to a UE-side TSN switch 36 from a CNC 32 of a TSN system 101. In block 820, the TSN support function 150 performs the operation of updating context of the UE-side TSN switch 36 and corresponding TSN-serving UE. The context is related to the TSN 101 such as the timing, the scheduling information (e.g., Tx and Rx windows), and the like. In block 830, the TSN support function 150 determines a QoS setting and scheduling assistance information concerning at least a PDU session (or communication session) relevant to the TSN-C information. The QoS setting means in exemplary embodiments, e.g., a delay budget, a guaranteed data rate, a reliability target such as packet error rate, and the like. The scheduling assistance information is related to the Tx/Rx window configured from the CNC 32, which may be, e.g., mapped to the serving 5G system as a time window forpacket scheduling or, e.g., semi-persistent scheduling configuration. The TSN support function 150 sends in block 840 the QoS setting and scheduling assistance information to at least one and up to all of the T SN serving UE 110, serving RAN node 170, and/or UPF 38. The sending uses, e.g., RRC and NAS signaling, on a C-plane of the serving 5G network 100 from the TSN support function 150 to the TSN serving UE 110 and the corresponding C-plane signaling of the serving 5G network 100 from TSN support function 150 to the serving RAN node 170 and UPF 38. The QoS setting and scheduling assistance information may then be used by these to manage the communication session in the serving 5G network 100 that is related to the TSN flow between two end stations 34-1, 34-2 in the time sensitive network 101, and that will pass through the switch (e.g., UE-side TSN switch 36), the UPF 38, and the UE 110. Block 840 is for the TSN support function 150 to configure the QoS/session

management-related information within the serving 5G network 100 in order for relevant 5G serving network entities (e.g. UE, RAN, UPF) to handle the PDU session according to TSN flow information. The 5G existing signaling may be reused for this purpose, but rather the additional trigger (i.e., TSN-C from CNC) is defined for the TSN support function 150 to send the QoS setting and scheduhng assistance information.

[00226] The TSN support function 150 in block 850 performs the operation of sending the updated TSN-C information to the UE-side TSN switch 36 via the serving 5G network 100. The sending uses, e.g., RRC and NAS signaling, on a C-plane of the serving 5G network 100. This step is for the TSN support function 150 to send the TSN-C information to UE-side TSN switch 36, which sending uses the TSN-C over C-plane of the serving 5G network 100.

[00227] 4. Additional exemplary details

[00228] On the UE side, there is a UE-side boundary TSN switch 36, also referred to as UE-side switch 36 for short, between a TSN end-station 34-1 and a UE 110, also referred to as a TSN-serving UE 110. It is via this in which a radio connection is provided to the UE-side switch 36, as opposed to the TSN end-station directly as in those alternatives that make the serving 5G network the ingress/egress TSN bridge for the TSN end-station. This allows for separating the TSN end-user or application domain from TSN transport domains including Ethernet and 5G. The use of the UE-side switch 36, more importantly, allows for leaving the strict timing determinism at the TSN domain. That is, the UE-side switch 36 is taking care of the strict timing determinism towards the TSN end-station 34-1. The UE-side switch 36 maybe integrated to the TSN-serving UE 110. Note that current UEs such as smart phones are already equipped with some sort of smart switch, likely high-speed Ethernet switch. Furthermore, a switch is considered as an essential and universal element of communication networks. In this case, the UE-side switch 36 can be considered as a part of UE capability of TSN-serving UE. The TSN-switch capability information may include, e.g., L2 address, numbers of input/output ports, data buffering capability, data switching capability, bandwidth, and/or additional supported IEEE TSN enhancements. [00229] The serving 5G network 100, particularly the TSN-support NF 150, may configure and control the UE-side switch 36, referred to as a secondary control, in line with the configuration and control provided by CNC 32 of the corresponding TSN system, referred to as a primary control. For this, the TSN-serving UE 110 is configured to deliver TSN-C messages of the UE-side switch 36 over a C-plane (e.g., the TSN C-plane and corresponding TSN-C signaling 510) of the serving 5G network 100 towards the TSN-support NF 150, as illustrated in FIG. 5 and described above. The serving 5G network 100, e.g., via the TSN-support NF 150, may initiate or terminate the primary control for the UE-side switch 36 towards to the primary TSN CNC 32. The secondary control, however, is invisible to the primary TSN CNC 32.

[00230] On the UPF side, it is assumed that UPF 8 of the serving 5G network

100 is connected to a TSN system 101 being served via a UPF-side TSN switch 37 (also called a UPF side boundary TSN switch 37). It is optional that the UPF-side TSN switch 37 is under control of the serving 5G network 100. However, it maybe beneficial for allowing the UPF-side TSN switch 37 to transmit to and receive from the UPF 38 with flexible timing which does not cause an impact on the timing set by the CNC 32 towards the corresponding TSN network 101 on the CN side. That is, the UPF-side switch 37 is taking care of the strict timing determinism towards the TSN network 101 on the CN side, while the timing towards the UPF 38 maybe according to the secondary TSN control from the serving 5G network 100.

[00231] With respect to the TSN-support NF 150, the TSN-support NF 150 is in an exemplary embodiment a TSN-aware C-plane NF which is between CNC 32 and TSN switches under control of the serving 5G network 100, i.e., at least UE-side TSN switch(es) 36, for a corresponding TSN system 101. This NF 150 is facilitated to know in an exemplary embodiment a common timing reference (e.g., a clock) of both the corresponding TSN system

101 and the serving 5G network 100. This NF 150 may provide the following functions and services towards at least UE-side TSN switch 36, TSN-serving UE 110, RAN node 170, and UPF 38 between the UE-side switch 36 and a corresponding UPF-side TSN switch 37 for transporting TSN related data between the two TSN switches 36, 37.

[00232] One function the TSN support function 150 may perform is to terminate and initiate TSN-C configuration and control procedures for a UE-side TSN switch, as illustrated in FIG. 9. FIG. 9 is a signaling diagram of TSN-C signaling over a C-plane of a serving 5G network for a UE-side TSN switch, in accordance with an exemplary embodiment. In FIG. 9, the UE side boundary TSN switch 36 is integrated with or connected to the TSN-serving UE 110 in block 910. The HE side boundary TSN switch 36 and the TSN serving UE 110 perform UE side activation in block 915. In general, this means the UE’s operation is activated. It maybe, e.g., the device is switched on, or device is plugged in, or the device starts to operate from idle mode, and the like, then the device starts to setup the connection to the TSN network 101. Meanwhile, the TSN support function 150 connects (block 905) to the CNC and gets a TSN timing reference.

[00233] In block 920, a connection set up is performed between the UE side boundary TSN switch 36 and CNC 32 using the TSN-serving UE 110 via the serving 5G network 100. The UE side boundary TSN switch 36 sends a TSN-C message in signaling 925 to the TSN-serving UE 110. In response, the TSN-serving UE 110 performs in block 930 RRC mapping for NAS signaling. This is to map the TSN-C message received from the UE side boundary TSN switch 36 to the correct RRC connection for a NAS signaling transmission. The TSN-serving UE 110 then sends a TSN-C message to the TSN support function 150 using, e.g., NAS signaling in signaling 935. In response, the TSN support function 150 in block 940 performs the operation of updating TSN switch information (info) and initiating TSN-C towards the CNC 32. The TSN support function 150 sends a TSN-C message to the CNC 32 in signaling 945.

[00234] In response to the TSN-C message, the CNC 32 computes TSN scheduling in block 950 and sends a response of a TSN-C message in signaling 955. The TSN support function 150 receives the response and in block 960 updates TSN switch information and initiates TSN-C towards a TSN switch, e.g., the UE side boundary TSN switch 36, by sending the TSN-C message in signaling 965 via the TSN-serving UE 110. The TSN-serving UE 110 receives this and, responsive to this, sends the TSN-C message in signaling 970.

[00235] This figure illustrates in part that the TSN-support NF 150 may maintain, set, and provide topology, capability and delay information related to an individual UE-side TSN switch 36 under control of the serving 5G network to CNC, and on behalf of the individual TSN switch 36. Additionally, the TSN-support NF 150 may communicate the computed scheduling received from the CNC 32 to the individual UE-side TSN switch 36 on an individual TSN flow basis.

[00236] Another function the TSN support function 150 may perform is triggering U-plane connection setup including a PDU session for interconnecting a UE-side TSN switch 36 to a corresponding UPF-side TSN switch 37 and TSN system 101 upon activation of the UE-side TSN switch 36, as illustrated in FIG. 10. FIG. 10 is a signaling diagram of a PDU session setup upon activation of a UE-side TSN switch, in accordance with an exemplary embodiment.

[00237] In FIG. 10, the blocks 910 and 915 have already been described. In block 1005, the UPF 38 and the UPF side boundary TSN switch 37 are interconnected. In block 1020, the TSN-serving UE 110 and the serving RAN node 170 perform an RRC connection set up.

[00238] Two exemplary options are detailed. In a first option (Option 1), the TSN-serving UE 110 reacts to the UE side activation from block 915, and the TSN-serving UE 110 sends (in signaling 1030) a connection setup request message that includes the TSN switch capability information. In a second option, the UE side boundary TSN switch 36 sends a TSN-C message in signaling 1025 to the TSN-serving UE 110, and the TSN-serving UE 110 communicates a corresponding TSN-C message to the TSN support function 150 using signaling 1035.

[00239] The TSN-support NF 150, upon receiving (see signaling 1030) a first TSN-C message from the UE-side switch or upon receiving (see signaling 1035) a request from the TSN serving UE 110 indicating an activation o f the UE-side switch 36, may determine and initiate a setup of a PDU session for interconnecting the UE-side TSN switch to the corresponding UPF-side TSN switch and TSN system. This occurs in block 1040. The TSN support function 150 also performs updating TSN switch information in block 1040. The PDU session may then be used for, e.g., TSN synchronization, link layer topology discovery, and/or management of the UE-side TSN switch towards the corresponding UPF-side TSN switch 37 and TSN system 101.

[00240] To set up the PDU session, the TSN support function 150 performs in block 1045 initiating the connection setup via the AMF/SMF 1090. Note that the AMF/SMF 1090 could be represented as AMF/SMF/PCF/AF, which means there is some function in the serving 5G network 100 that performs some or all of these functions. In block 1050, a communication session, such as a PDU session, and associated DRB set up is performed between the TSN-serving UE 110 and UPF 38, and between the TSN-serving UE 110 and the RAN node 170 under the control of the TSN support function 150 and the AMF/SMF 1090. The PTP or LLDP (or other) communication can then be enabled over the established PDU session in block 1055. [00241] Another function the TSN support function 150 may perform is QoS setting and scheduling assistance for a PDU session and RB service of a TSN-serving UE corresponding to one or more TSN flows of one or more TSN end stations, especially in terms of delay budgets, as illustrated in FIG. 11. This figure is a signaling diagram of QoS setting and scheduling assistance for a TSN-related PDU session, in accordance with an exemplary embodiment.

[00242] The TSN support function 150 and other C-plane NFs perform in block 1105 getting TSN timing reference and switch information either from the UE side TSN switch 36 or the CNC 32. In block 1110, the TSN-serving UE 110, serving RAN node 170, UPF 38 and TSN support function 150 perform PDU session(s) and DRB(s) establishment for interconnecting to the TSN system 101 and serving individual TSN flow(s) between a UE-side switch 36 and a UPF-slde switch 37. Note that a PDU session is one example, but other communication sessions may be established. In block 1115, the TSN support function 150 performs the operation of determining a QoS setting and scheduling assistance, e.g., a delay budget for a TSN-related PDU session. The TSN support function 150 sends QoS setting and scheduling assistance messaging to the UPF 38, serving RAN node 170, and TSN-serving UE 110, in signaling 1120, 1125, and 1130, respectively.

[00243] Based on received CNC- computed scheduling information and absolute time references of both TSN and serving 5G network, the TSN support function 150 may determine the maximum time or delay budget for a PDU session and RB service in UL and DL. Alternatively or in addition, based on maximum neighbor propagation delay threshold of media-dependent ports of UPF side and UE side time-aware relays, the TSN support function 150 may determine the maximum delay budget for a PDU session and RB service in UL and DL to enable forwarding of PTP messages on those ports. Alternatively or in addition, based on the determined delay budget, the TSN support function 150 may trigger QoS setting and scheduling requirements towards the UPF 38, serving RAN node 170, and UE 110.

[00244] Examples for QoS setting and scheduling assistance include one or both of the following.

[00245] 1) Time offsets and delay constraints may be used and these can be mapped on QCIs. [00246] 2) TSN end-station’ s multiplexing may be performed in case the

TSN-serving UE 110 is serving a number of synchronized TSN end-stations 34 and services (e.g., of identical control loops).

[00247] The“5G as TSN link” structure 500 allows for a clear separation or functional split between the 5G and TSN domains. Therefore, there is no need for the serving 5G network 100 and TSN network 101 to share or synchronize to the same clock or use the same synchronization mechanism. It is flexible for the serving 5G network to adopt timing offset or compensation techniques as referred to the timing of TSN being served. In this regard, the serving 5G network 100 may need to know the TSN timing related to at least the two boundary TSN switches of each“5G as TSN link” structure.

[00248] This enhanced network function TSN-support NF 150 may be a part of AMF, SMF and/or PCF for examples. It is noted that, for a network-initiated operation, the TSN-support NF 150 may also trigger paging and activation of both the TSN-serving UE 110 and associated UE-side TSN switch 36 if the connection request is from the network side e.g. from CNC.

[00249] Note that TSN-support NF 150 may initiate configuration and control towards the UE-side TSN switch 36 as soon as the TSN serving UE 110 is connected to the serving 5G network 100, even before setting up a U-plane connection for interconnecting the UE-side TSN switch 36 to the corresponding UPF-side TSN switch 37 and TSN system 101.

[00250] UE assistance information may be used in addition to or instead of UE capability for the TSN-serving UE 110 to indicate about the associated UE-side TSN switch 36, e.g., in cases when the UE-side TSN switch 36 is not integrated into the TSN serving UE 110 and when indicating about more dynamic information such as TSN flow, available bandwidth, or timing information.

[00251] 5. Support of TSN flows

[00252] We use the following example for an illustration of TSN flows and how

TSN switches maybe configured to serve a TSN flow. This example uses information from Cisco,“Time-Sensitive Networking: A Technical Introduction,” White paper (2017).

[00253] Refer to FIG. 12, illustrates physical topology for an example workflow and how TSN switches maybe configured to serve a TSN flow. This figure is a modified version of a figure from the Cisco White paper. There are two TSN bridges 1210-1 and 1210-2 and two TSN end devices 1220-1 and 1220-2 (labeled as tsn-TLl and tsn-TL2, respectively). There are two flows, flow 1 1230-1 and flow 2 1230-2 between the two TSN end devices 1220-1 and 1220-2. Flow 1 1230-1 goes from TSN end device 1220-1 to TSN end device 1220-2, and flow 2 1230-2 goes from TSN end device 1220-2 to TSN end device 1220-1. A number of interfaces are shown: Gi 1/5 between the TSN bridge 1210-1 and the TSN end device 1220-1; Gil/4 between the two TSN bridges 1210-1 and 1210-2; and Gi 1/6 between the TSN bridge 1210-2 and the TSN end device 1220-2.

[00254] For the example in the Cisco White paper, they used the following: “When transmitting a TSN flow, the talker is given a window to transmit. The window is approximately 13ps wide in terms of time (for links operating at Gigabit speeds). The l3gs is required to account for the chance that a large 1518-byte Ethernet frame will be transmitted just before the TSN flow Ethernet frame and will delay the TSN flow by ~l2ps. A 64-byte frame takes 0.7ps to transmit.” The talker is one of the TSN end devices 1220-1 or 1220-2.

[00255] Consider that TSN bridge 1210-1 and TSN bridge 1210-2 are replaced with the UE-side switch 36 and UPF-side switch 37 as illustrated by FIG. 12. An exemplary embodiment herein allows for 5G to have a say on the constraint of the transport delay between the UE-side and UPF-side switches; to merge the transport delay constraint with the time window of the UPF-side switch for the UL delay budget for flowl; to merge the transport delay constraint with the time window of the UE-side switch for the DL delay budget for flow2; and to make use of the delay budget flexibly and efficiently within the 5G domain

[00256] FIG. 13 provides an illustration of a time budget for the serving 5G to deliver TSN UL and DL, according to an embodiment. This illustrates the following 5GN (5G network) timing: the Maximum UL/DL time budget for the serving 5G network; the Minimum DL time budget for the serving 5G network; and the Minimum UL time budget for the serving 5G network. This figure also illustrates the following TSN timing: the TSN RxWs for both the UPF side boundary TSN switch 37 and UPF side boundary TSN switch 37 and the timing offset between TSN timing and 5GN timing.

[00257] TSN-support NF may also create and use a“virtual” TSN switch in between a pair of UE-side and UPF-side switches 36, 37, respectively to get computed scheduling information from the CNC 32 for the virtually decomposed TSN transport connection, as illustrated in FIG. 14. FIG. 14 is a block diagram of one possible and non-limiting exemplary system, similar to the system in FIG. 4A but implementing a TSN switch within the serving 5G network, in accordance with an exemplary embodiment. The virtual (or actual) TSN switch 1436 is connected to the UE 110 via a link 42’ and to the UPF 38 via a link 44’. Though the virtual TSN switch 1436 is illustrated in FIG. 14 as a standalone entity. It maybe implemented in any network entity, e.g. the RAN node 170 of the serving 5G network.

[00258] As illustrated in FIG. 15, there are additional 5GN timings for the virtual switch TSN 1436 : a time budget of decomposed link such as for radio part (as a reference value in case of a virtual TSN switch) and a time budget of a decomposed link such as for the CN part of the serving 5G network 100. Due to introduction of the additional TSN switch within the serving 5G network 100, additional TSN scheduling information such as TSN RxW is provided from the CNC 32 and the timing offset between TSN timing and corresponding 5GN timing in the different decomposed links may be different.

[00259] In more detail, this allows for utilizing CNC computed scheduling information to manage the transport connection provided by the serving 5G network 100 such as for provisioning and monitoring of corresponding PDU session and RB. For example, if it is preferable for the serving 5G network 100 to control the CN part and the RAN part separately then a virtual switch 1436 maybe created to decompose the 5G transport connection between the UE-side switch 36 and the UPF-side switch 37 into two parts (illustrated inpart by the links 42’ and 44’) with the virtual switch 1436 in between. The virtual switch 1436 also gets computed scheduling from the CNC 32 but the serving 5G network 100 does not have to follow the CNC computed scheduling on the virtual switch 1436 but rather uses that as some provisioned parameters to trigger certain control to either the RAN part (e.g., the RAN node 170) or the CN part (e.g., the AMF 40/SMF 42/PCF 44 and the like).

[00260] 6. Additional description

[00261] As used in this application, the term“circuitry” may refer to one or more or all of the following:

[00262] (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

[00263] (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with

software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processors)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and [00264] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[00265] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[00266] Embodiments herein may be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware. In an example embodiment, the software (e.g., application logic, an instruction set) is maintained on anyone of various conventional computer-readable media. In the context of this document, a“computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted, e.g., in FIG. 4B. A computer-readable medium may comprise a computer-readable storage medium (e.g., memories 125, 155, 171 or other device) that maybe any media or means that can contain, store, and/or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer-readable storage medium does not comprise propagating signals.

[00267] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.

[00268] Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. [00269] It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

CLAIMS What is claimed is:

1. A method, comprising:

indicating, by a user equipment in a wireless communications system, a capability of serving a time sensitive network, the indicating performed by the user equipment toward the wireless communications system;

receiving, by the user equipment, control information for the time sensitive network from a switch in the time sensitive network and coupled to the user equipment; and

sending, by the user equipment, the received control information for the time sensitive network toward the wireless communication system.

2. The method of claim 1 , wherein:

the sending the received control information for the time sensitive network toward the wireless communication system uses at least one of radio resource control signaling and non-access stratum signaling on a control plane configured to transport the control information for the time sensitive network.

3. The method of claim 2, wherein:

the control plane used to transport the received control information between the user equipment and the wireless communication system is carried over at least one interface configured between the user equipment and corresponding one or more communication elements of the wireless communication system.

4. The method of any of claims 1 to 3, wherein the receiving the control information from the switch is carried over an interface configured between the switch and the user equipment.

5. The method of any of claims 1 to 4, wherein the sending the received control

information for the time sensitive network toward the wireless communication system is performed for use by the wireless communication system to manage control of a communication session of a time sensitive network flow between two end stations in the time sensitive network that will pass through at least the switch and the user equipment of the wireless communication system.

6. The method of any of claims 1 to 5, wherein the sending the received control

information for the time sensitive network toward the wireless communication system is performed for use by the time sensitive network system at least by exchanging, between the switch and the time sensitive network system and passing through the user equipment, control signaling of the time sensitive network for one or more of the following: network topology discovery, capability information, and scheduling information.

7. The method of any of claims 1 to 6, wherein the control of the communication session is managed for at least a connection set up, and the method further comprises the user equipment participating in the connection set up of the communication session for the time sensitive network flow between the two end stations in the time sensitive network and passing through the user equipment.

8. The method of claim 7, further comprising the user equipment participating in the communication session for the time sensitive network flow between the two end stations in the time sensitive network and passing through the user equipment.

9. The method of any of claims 7 or 8, wherein:

the switch is a first switch connected to one of the two end stations;

the time sensitive network flow between the two end stations in the time sensitive network also passes through a user plane function in the wireless communication system;

the user plane function is connected to a second switch that is in the time sensitive network and is connected to an other of the two end stations; and the communication session for the time sensitive network flow p sses through both the user equipment and the user plane function.

10. A method, comprising:

receiving, at a network element in a wireless communication system, control

information of a switch from a user equipment serving the time sensitive network system via the switch and in the wireless communication system, wherein the switch is in the time sensitive network system and the control information is targeted to a centralized network configuration entity in the time sensitive network system;

updating by the network element context of the user equipment and the switch; and sending by the network element the received control information including the updated context of the user equipment and the switch toward the centralized network configuration entity of the time sensitive network system.

11. The method of claim 10, wherein:

the receiving the control information of the time sensitive network uses a control plane of the wireless communication system configured to transport the control information for the time sensitive network system; and

the control plane used to receive the control information is carried over an interface configured between the network element and the user equipment

12. The method of any of claims 10 or 11 , wherein:

the sending the received control information uses a control plane; and

the control plane used to send the received control information is carried over an interface configured between the network element and the centralized network configuration entity.

13. The method of any of claims 10 to 12, wherein the sending the received control information for the time sensitive network system toward the time sensitive network system is performed for use by the time sensitive network system to manage control of a time sensitive network flow between two end stations in the time sensitive network and passing through at least the switch and the user equipment of the wireless communication system.

14. The method of claim 13 , wherein the control of the time sensitive network flow is managed at least by exchanging, between the switch and the centralized network configuration of the time sensitive network and passing through the network entity, control signaling of the time sensitive network system for one or more of the following: network topology discovery, capability information, and scheduling information.

15. The method of any of claims 13 or 14, further comprising the network element

participating in a connection set up of a communication session in the wireless communication network for the time sensitive network flow between the two end stations in the time sensitive network and passing through the user equipment.

16. A method, comprising:

receiving, at a network element in a wireless communication system, control

information of a switch in a time sensitive network, the control information received from a centralized network configuration entity of the time sensitive network;

updating, by the network element, context of the switch and a corresponding user equipment serving the time sensitive network and in the wireless communication system;

determining by the network element a quality of service setting and scheduling

assistance information concerning at least a communication session corresponding to the control information;

sending by the network element the quality of service setting and scheduling assistance information to at least one and up to all of the following elements in the wireless communication system: user equipment, a serving radio access network node, and a user plane function; and

sending by the network element the updated control context to the switch via the user equipment.

17. The method of claim 16, wherein:

the receiving the control information uses a control plane of the wireless

communication system configured to transport the control information for the time sensitive network system; and

the control plane used to receive the control information is carried over an interface configured between the network element and the centralized network configuration entity.

18. The method of any of claims 16 or 17, wherein:

the sending the received control information of the time sensitive network uses a control plane of the wireless communication system configured to transport the control information for the time sensitive network system; and the control plane used to send the received control information is carried over an interface configured between the network element and the user equipment.

19. The method of any of claims 16 to 18, wherein the sending by the network element the quality of service setting and scheduling assistance information is performed for use by the elements to manage the communication session in the wireless communication system for a time sensitive network flow between two end stations in the time sensitive network and passing through the serving radio access network node, the user plane function and the user equipment of the wireless communication network.

20. The method of any of claims 16 to 19, further comprising the network element

participating in a connection set up of a communication session in the wireless communication network for the time sensitive network flow between the two end stations in the time sensitive network and passing through the serving radio access network node, the user plane function and the user equipment of the wireless communication network.

21. A computer program, comprising code for performing the methods of any of claims 1 to 20, when the computer program is run on a processor.

22. The computer program according to claim 21, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer.

23. The computer program according to claim 21 , wherein the program is directly loadable into an internal memory of the computer.

24. An apparatus, comprising:

means for indicating, by a user equipment in a wireless communications system, a capability of serving a time sensitive network, the means for indicating performed by the user equipment toward the wireless communications system; means for receiving, by the user equipment, control information for the time sensitive network from a switch in the time sensitive network and coupled to the user equipment; and

means for sending, by the user equipment, the received control information for the time sensitive network toward the wireless communication system.

25. The apparatus of claim 24, wherein:

the means for sending the received control information for the time sensitive network toward the wireless communication system uses at least one of radio resource control signaling and non-access stratum signaling on a control plane configured to transport the control information for the time sensitive network.

26. The apparatus of claim 25, wherein:

27. The apparatus of any of claims 24 to 26, wherein the means for receiving the control information from the switch is performed using an interface configured between the switch and the user equipment.

28. The apparatus of any of claims 24 to 27, wherein the means for sending the received control information for the time sensitive network toward the wireless communication system is performed for use by the wireless communication system to manage control of a communication session of a time sensitive network flow between two end stations in the time sensitive network that will pass through at least the switch and the user equipment of the wireless communication system.

29. The apparatus of any of claims 24 to 28, wherein the means for sending the received control information for the time sensitive network toward the wireless communication system is performed for use by the time sensitive network system at least by means for exchanging, between the switch and the time sensitive network system and passing through the user equipment, control signaling of the time sensitive network for one or more of the following: network topology discovery, capability information, and scheduling information.

30. The apparatus of any of claims 24 to 29, wherein the control of the communication session is managed for at least a connection set up, and the apparatus further comprises means for participating by the user equipment in the connection set up of the communication session for the time sensitive network flow between the two end stations in the time sensitive network and passing through the user equipment.

31. The apparatus of claim 30, further comprising means for participating by the user equipment in the communication session for the time sensitive network flow between the two end stations in the time sensitive network and passing through the user equipment.

32. The apparatus of any of claims 30 or 31, wherein:

the switch is a first switch connected to one of the two end stations;

the user plane function is connected to a second switch that is in the time sensitive network and is connected to an other of the two end stations; and the communication session for the time sensitive network flow passes through both the user equipment and the user plane function.

33. An apparatus, comprising:

means for receiving, at a network element in a wireless communication system, control information of a switch from a user equipment serving the time sensitive network system via the switch and in the wireless communication system, wherein the switch is in the time sensitive network system and the control information is targeted to a centralized network configuration entity in the time sensitive network system;

means for updating by the network element context of the user equipment and the switch; and

means for sending by the network element the received control information including the updated context of the user equipment and the switch toward the centralized network configuration entity of the time sensitive network system.

34. The apparatus of claim 33, wherein:

the means for receiving the control information of the time sensitive network uses a control plane of the wireless communication system configured to transport the control information for the time sensitive network system; and the control plane used to receive the control information is carried over an interface configured between the network element and the user equipment.

35. The apparatus of any of claims 33 or 34, wherein:

the means for sending the received control information uses a control plane; and the control plane used to send the received control information is carried over an

interface configured between the network element and the centralized network configuration entity.

36. The apparatus of any of claims 33 to 35, wherein the means for sending the received control information for the time sensitive network system toward the time sensitive network system is performed for use by the time sensitive network system to manage control of a time sensitive network flow between two end stations in the time sensitive network and passing through at least the switch and the user equipment of the wireless communication system.

37. The apparatus of claim 36, wherein the control of the time sensitive network flow is managed at least by means for exchanging, between the switch and the centralized network configuration of the time sensitive network and passing through the network entity, control signaling of the time sensitive network system for one or more of the following: network topology discovery, capability information, and scheduling information.

38. The apparatus of any of claims 36 or 37, further comprising means for participating by the network element in a connection set up of a communication session in the wireless communication network for the time sensitive network flow between the two end stations in the time sensitive network and passing through the user equipment.

39. An apparatus, comprising:

means for receiving, at a network element in a wireless communication system, control information of a switch in a time sensitive network, the control information received from a centralized network configuration entity of the time sensitive network;

means for updating, by the network element, context of the switch and a corresponding user equipment serving the time sensitive network and in the wireless communication system;

means for determining by the network element a quality of service setting and

scheduling assistance information concerning at least a communication session corresponding to the control information;

means for sending by the network element the quality of service setting and scheduling assistance information to at least one and up to all of the following elements in the wireless communication system: user equipment, a serving radio access network node, and a user plane function; and

means for sending by the network element the updated control context to the switch via the user equipment.

40. The apparatus of claim 39, wherein:

the means for receiving the control information uses a control plane of the wireless communication system configured to transport the control information for the time sensitive network system; and

41. The apparatus of any of claims 39 or 40, wherein:

the means for sending the received control information of the time sensitive network uses a control plane of the wireless communication system configured to transport the control information for the time sensitive network system; and the control plane used to send the received control information is carried over an interface configured between the network element and the user equipment.

42. The apparatus of any of claims 39 to 41 , wherein the means for sending by the network element the quality of service setting and scheduling assistance information is performed for use by the elements to manage the communication session in the wireless communication system for a time sensitive network flow between two end stations in the time sensitive network and passing through the serving radio access network node, the user plane function and the user equipment of the wireless communication network.

43. The apparatus of any of claims 39 to 42, further comprising means for participating by the network element in a connection set up of a communication session in the wireless communication network for the time sensitive network flow between the two end stations in the time sensitive network and passing through the serving radio access network node, the user plane function and the user equipment of the wireless communication network.

44. A communication system comprising an apparatus according to any of claims 24 to 32 and an apparatus according to any of claims 33 to 43.

45. The communication system of claim 44, further comprising the time sensitive network system.