Transport network slicing control device and control plane entity for transport network based on time-sensitive network

Abstract

The present invention relates to a transport network slice control device and a TSN control plane entity of a transport network (TN) based on a time-sensitive network (TSN). The transport network slice control device includes: a first interface configured to communicate with a transport network slice management entity of a mobile network; and a second interface configured to communicate with the TSN control plane entity.

Description

Technical Field

[0001] The present invention generally relates to the field of communication networks, and more particularly to an apparatus and method for interconnecting a network slice control management system of a mobile network with a time-sensitive network (TSN) control plane.

[0002] To this end, the present invention provides a transport network slice control device, a TSN control plane entity for a TSN-based transport network (TN), and a corresponding method. The transport network slice control device is configured to communicate with a transport network slice management entity of a mobile network and is configured to communicate with a TSN control plane entity of a TSN-based TN. In addition, the TSN control plane entity is configured to communicate with the transport network slice control device of the mobile network. Background Art

[0003] Generally, network slicing is a design paradigm that enables sharing of resources and functions on a per-slice basis. Furthermore, the Service and System Aspects (SA) of the Third Generation Partnership Project (3GPP), which includes the SA1, SA2, and SA5 groups, are studying architectural and procedural issues related to network slicing. Furthermore, using network slicing in the same fifth generation (5G) system, multiple network slice instances can operate simultaneously to support ultra-reliable (UR) low-latency communications (URLLC) and enhanced mobile broadband (eMBB), where specific user flows can be associated with specific network slices.

[0004] In addition, the 3GPP SA and Radio Access Network (RAN) groups are creating technical specifications to combine the slicing concepts of the RAN and Core to create end-to-end network slicing.

[0005] For example, 3GPP SA1 provides use cases that can be implemented via network slicing. Furthermore, 3GPP SA2 discusses an architecture for implementing network slicing in 3GPP networks. The architecture is described in TS 23.501, with signaling described in TR 23.799 and TS 23.502, among others, and network management and orchestration aspects described in 3GPP SA5.

[0006] Regarding the transport network (TN), 3GPP provides the relevant network slice management TN Network Slice Subnet Management Function (NSSMF) entity. This entity is responsible for the lifecycle management of transport network slice instances. However, 3GPP is not responsible for the actual operation and control of the TN. As these requirements are driving the deployment and configuration of transport network technologies, different technologies have been proposed and are currently in operation to meet network slicing requirements.

[0007] The Internet Engineering Task Force (IETF) specifies a "transport slice multilayer controller" to resolve, for example, TN requirements on a per-slice basis. However, the actual operation of the transport network depends on technology-specific configuration and optimization.

[0008] IEEE Time-Sensitive Networking (TSN) is a technology that enables deterministic performance guarantees in transport networks. For example, TS 23.501, TS 23.502, and TS 23.503 describe how to incorporate 5G systems into TSN bridges. Furthermore, from the IEEE's perspective, 802.1CM is the result of a collaboration between CPRI and IEEE 802.1 to develop TSN as a solution for fronthaul links. 802.1CM describes how to meet stringent fronthaul requirements in Ethernet-based bridged networks. TSN networks can support not only fronthaul services, but also other types of services traversing the network simultaneously, and provide deterministic communication not only in terms of throughput, but also in terms of latency and jitter.

[0009] There is a general need for improved devices and methods for supporting TSN in mobile networks. Summary of the Invention

[0010] In view of the above problems and shortcomings, the embodiments of the present invention aim to improve traditional transport network slicing control equipment and time-sensitive network (TSN) control plane entities and methods for communication networks.

[0011] One objective is to connect a network slice control management system (e.g., a transport network slice control device) with a TSN control plane (e.g., a TSN control plane entity). For example, one or more interfaces should be able to manage network slices of an IEEE TSN-based network. In addition, a TSN control plane entity should be provided that can support network slicing features.

[0012] Another goal is to enable network slicing through a unified transport network based on IEEE TSN. For example, in the case of a disaggregated RAN, TSN technology can be used to support backhaul and midhaul connections in addition to fronthaul links.

[0013] Another objective is to dynamically signal network slicing requirements from the 3GPP mobile network to the TSN CUC / CNC control plane. For example, the 3GPP mobile network can dynamically map slicing requests to the underlying TSN network, while the TSN network can also report service requirements to the 3GPP mobile network so that relevant resource allocation can be performed on a per-network slice basis.

[0014] One or more objects are achieved by the embodiments of the invention as described in the accompanying independent claims. Advantageous implementations of the embodiments of the invention are further defined in the dependent claims.

[0015] A first aspect of the present invention provides a transport network slice control device, wherein the transport network slice control device includes: a first interface configured to communicate with a transport network slice management entity of a mobile network, and a second interface configured to interface with a TSN control plane entity of a transport network (TN) based on a time-sensitive network (TSN).

[0016] The transport network slice control device can be a physical entity (e.g., an electronic device such as a computer or server) or a logical entity, or can be included in it. For example, the transport network slice control device can be a transport slice multi-layer controller. The multi-layer controller not only considers TSN-related information, but also other Layer 2, Layer 3, and Layer 4 network operations such as VLAN.

[0017] The transport network slice control device includes: a first interface, which can communicate with a transport slice management entity. For example, the transport slice management entity can be a TN-Network Slice Subnet Management Function (TN-NSSMF) entity of the mobile network.

[0018] The transport network slice control device further includes: a second interface that can interface with a TSN control plane entity. For example, the TSN control plane entity can be a control plane of a transport network based on IEEE TSN.

[0019] For example, the transport network slice control device according to the first aspect (e.g., a transport slice multi-layer controller) may include a first interface and a second interface, the first interface being used to implement communication with a transport slice management entity of a mobile network (e.g., an NSSMF entity of a mobile network), and the second interface being used to implement communication with a control plane entity of a TSN-based TN (e.g., a control plane of a transport network based on IEEE TSN).

[0020] In an implementation of the first aspect, the transport network slice control device is further configured to: send network slice control and management information to a transport network slice management entity of the mobile network via a first interface or receive network slice control and management information from the transport network slice management entity, and / or send network slice control and management information required for the TSN network to a TSN control plane entity via a second interface or receive network slice control and management information required for the TSN network from the TSN control plane entity.

[0021] Specifically, the transport network slicing control device can realize the ability to open the performance attributes and requirements of the TSN-based transport network to the 3GPP mobile network.

[0022] In another implementation of the first aspect, the network slice management information includes one or more of the following:

[0023] -TSN-TN network slicing requirements information,

[0024] -TSN-TN slice instance creation request,

[0025] -TSN-TN slice instance creation response,

[0026] -TSN-TN slice instance status information,

[0027] -TSN-TN slice instance strategy information,

[0028] -TSN-TN slice instance configuration information,

[0029] -TSN-TN slice instance running action,

[0030] -TSN-TN slice instance deactivation action,

[0031] -Soft TSN slicing instance capability,

[0032] -Hard TSN slicing instance capability.

[0033] In another implementation of the first aspect, the transport network slice control device is further configured to: receive updated TN slice information or updated TN slice resource provision from the transport slice management entity of the mobile network via the first interface, and / or send updated TN slice information or updated TN slice resource provision to the TSN control plane entity via the second interface.

[0034] For example, the transport network slice control device can receive TSN updates on a per TSN slice basis, TSN updates of flow performance, user slice participation updates, etc.

[0035] In another implementation of the first aspect, the transport network slice control device is further configured to: receive a TN slice isolation requirement from a transport slice management entity of the mobile network, and maintain TN slice isolation on a TSN-based data plane according to the received TN slice isolation requirement.

[0036] A second aspect of the present invention provides a TSN control plane entity for a transport network (TN) based on a time-sensitive network (TSN), wherein the TSN control plane entity is configured to: receive network slice management information delivered from a transport slice management entity of a mobile network through a transport network slice control device, open capability information of the TSN-based TN to the network slice transport network control device, and provide capability information of the TSN-based TN to the network slice transport network control device.

[0037] The TSN control plane entity can be a physical entity (e.g., an electronic device such as a computer or server computer) or a logical entity, or can be included therein. For example, the TSN control plane entity can be a centralized user configuration (CUC) or a centralized network configuration (CNC) of a transport network based on IEEE TSN.

[0038] In one implementation of the second aspect, the TSN control plane entity is further configured to: store information in a network slice database, and provide information related to the life cycle of one or more transport network slice instances to the control plane entity of the TSN-based TN.

[0039] In another implementation of the second aspect, the network slice management information includes one or more of the following:

[0040] -TSN-TN network slicing requirements information,

[0041] -TSN-TN slice instance creation request,

[0042] -TSN-TN slice instance creation response,

[0043] -TSN-TN slice instance status information,

[0044] -TSN-TN slice instance strategy information,

[0045] -TSN-TN slice instance configuration information,

[0046] -TSN-TN slice instance running action,

[0047] -TSN-TN slice instance deactivation action,

[0048] -Soft TSN slicing instance capability,

[0049] -Hard TSN slicing instance capability.

[0050] In another implementation of the second aspect, the TSN control plane entity is further configured to: obtain determined TN performance attributes from the transport network slice control device, and map the network slice management information received from the transport slice management entity of the mobile network to the TSN-specific performance attributes of the TSN-based TN on a per-slice basis based on the determined TN performance attributes.

[0051] For example, the TSN control plane entities can perform specific optimizations based on the network slice instance description defined by 3GPP and perform the necessary resource allocation for the underlying transport topology and link interconnection taking into account the required transport network performance attributes.

[0052] In another implementation of the second aspect, the TSN control plane entity is further configured to: receive, from the transport network slice control device, a TN slice isolation requirement received from the network slice transport network management entity of the mobile network, and maintain TN slice isolation on the TSN-based data plane according to the received TN slice isolation requirement.

[0053] For example, when using 802.1Qbv, the TSN control plane entity can use a specific scheduler and Gate Control List (GCL) to support slice isolation in the converged TSN-based data plane.

[0054] In another implementation of the second aspect, the TSN control plane entity is based on a network slice-aware TSN control plane entity, and the network slice-aware TSN control plane entity includes: a centralized network configuration (CNC) TSN control entity, which is configured to control the TSN TN network slice subnet instance (NSSI), or a centralized user configuration (CUC) TSN control entity, which is configured to deliver requirements such as TSN TN-NSSI flow specifications to the CNC.

[0055] Specifically, the interface between the CUC / CNC and the transport network slice controller is called the "TSN slice awareness interface", which can be an interface for interconnecting the network slice control management system with the TSN centralized control plane.

[0056] In another implementation of the second aspect, the CNC is further configured to control TSN slice-aware operations and / or non-TSN slice-aware operations.

[0057] In another implementation of the second aspect, the TSN control plane entity includes: a database configured to store resource allocation information and / or resource identification and mapping information about flow performance attributes for each TN NSSI.

[0058] A third aspect of the present invention provides a system comprising: at least one transport network slice control device for a mobile network according to the first aspect or any implementation thereof, and at least one time TSN control plane entity for a transport network (TN) based on a sensitive network (TSN) according to the second aspect or any implementation thereof.

[0059] A fourth aspect of the present invention provides a method for a transport network slice control device for a mobile network, wherein the method includes: communicating with a transport network slice management entity of the mobile network via a first interface, and communicating with a TSN control plane entity of a transport network (TN) based on a time-sensitive network (TSN) via a second interface.

[0060] In an implementation of the fourth aspect, the method also includes: sending network slice control and management information to a transport network slice management entity of the mobile network via a first interface or receiving network slice control and management information from the transport network slice management entity, and / or sending network slice control and management information required for the TSN network to a TSN control plane entity via a second interface or sending or receiving network slice control and management information required for the TSN network from the TSN control plane entity.

[0061] In another implementation of the fourth aspect, the network slice management information includes one or more of the following:

[0062] -TSN-TN network slicing instance requirement information,

[0063] -TSN-TN slice instance creation request,

[0064] -TSN-TN slice instance creation response,

[0065] -TSN-TN slice instance status information,

[0066] -TSN-TN slice instance strategy information,

[0067] -TSN-TN slice instance configuration information,

[0068] -TSN-TN slice instance running action,

[0069] -TSN-TN slice instance deactivation action,

[0070] -Soft TSN slicing instance capability,

[0071] -Hard TSN slicing instance capability.

[0072] In another implementation of the fourth aspect, the method also includes: receiving updated TN slice information or updated TN slice resource allocation from a transport slice management entity of the mobile network via a first interface, and / or sending updated TN slice information or updated TN slice resource allocation to a TSN control plane entity via a second interface.

[0073] In another implementation of the fourth aspect, the method also includes: receiving a TN slice isolation requirement from a transport slice management entity of a mobile network, and maintaining TN slice isolation on a TSN-based data plane according to the received TN slice isolation requirement.

[0074] The method according to the fourth aspect realizes the advantages and effects described for the transmission network slice control device of the first aspect.

[0075] A fifth aspect of the present invention provides a method for a TSN control plane entity of a transport network (TN) based on a time-sensitive network (TSN), wherein the method includes: receiving network slice management information delivered from a transport slice management entity of a mobile network through a transport network slice control device, opening capability information of the TSN-based TN to the network slice transport network control device, and providing capability information of the TSN-based TN to the network slice transport network control device.

[0076] In an implementation of the fifth aspect, the method further includes: storing information in a network slice database, and providing information related to the life cycle of one or more transport network slice instances to a control plane entity of a TSN-based TN.

[0077] In another implementation of the fifth aspect, the network slice management information includes one or more of the following:

[0078] -TSN-TN network slicing requirements information,

[0079] -TSN-TN slice instance creation request,

[0080] -TSN-TN slice instance creation response,

[0081] -TSN-TN slice instance status information,

[0082] -TSN-TN slice instance strategy information,

[0083] -TSN-TN slice instance configuration information,

[0084] -TSN-TN slice instance running action,

[0085] -TSN-TN slice instance deactivation action,

[0086] -Soft TSN slicing instance capability,

[0087] -Hard TSN slicing instance capability.

[0088] In another implementation of the fifth aspect, the method also includes: obtaining determined TN performance attributes from a transport network slice control device, and mapping the network slice management information received from a transport slice management entity of a mobile network to TSN-specific performance attributes of a TSN-based TN on a per-slice basis based on the determined TN performance attributes.

[0089] In another implementation of the fifth aspect, the method also includes: receiving, from the transport network slice control device, a TN slice isolation requirement received from a network slice transport network management entity of the mobile network, and maintaining TN slice isolation on a TSN-based data plane according to the received TN slice isolation requirement.

[0090] In another implementation of the fifth aspect, the TSN control plane entity is based on the network slice-aware TSN control plane entity, wherein the method further includes: the TSN CNC control entity of the network slice-aware TSN control plane controls the TSN TN-NSSI, or the TSN CUC transmits the TSN TN-NSSI flow specification and other requirements to the CNC.

[0091] In another implementation of the fifth aspect, the method further includes: controlling the TSN slice-aware operation and / or the non-TSN slice-aware operation by the CNC.

[0092] In another implementation of the fifth aspect, the method further includes: storing, by a TSN control plane entity including a database, resource allocation information and / or resource identification and mapping information about flow performance attributes for each TN NSSI.

[0093] The method according to the fifth aspect realizes the advantages and effects of the TSN control plane entity description according to the second aspect.

[0094] A sixth aspect of the present invention provides a computer program comprising program code for executing the method according to the fourth aspect or the fifth aspect or any implementation thereof.

[0095] A seventh aspect of the present invention provides a non-transitory storage medium storing executable program code, which, when executed by a processor, causes the method according to the fourth aspect or the fifth aspect or any implementation thereof to be performed.

[0096] It should be noted that all devices, elements, units and modules described in this application can be implemented in software or hardware elements or any combination thereof. The steps performed by the various entities described in this application and the functions to be performed by the various entities described are intended to refer to that each entity is suitable for or used to perform each step and function. Even if in the description of the following specific embodiments, the specific function or step to be performed by an external entity is not reflected in the description of the specific detailed elements of the entity that performs the specific step or function, the technician should be aware that these methods and functions can be implemented in the corresponding software or hardware elements, or in any combination of such elements. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] The following description of specific embodiments in conjunction with the accompanying drawings will illustrate the above aspects and implementation methods, wherein:

[0098] Figure 1 A schematic diagram showing a transport network slicing control device according to an embodiment of the present invention is shown;

[0099] Figure 2A schematic diagram illustrating a TSN control plane entity for a TSN-based TN according to an embodiment of the present invention is shown;

[0100] Figure 3 A schematic diagram showing a system including a transport network slice control device for a mobile network and a TSN control plane entity for a TSN-based TN according to an embodiment of the present invention is shown;

[0101] Figure 4 A schematic diagram of a network slice management entity including a transport slice control device is shown;

[0102] Figure 5 A schematic diagram illustrating an exemplary transport network of a 5G mobile network for a disaggregated RAN is shown;

[0103] Figure 6 A schematic diagram illustrating a 5G system as a TSN bridge is shown;

[0104] Figure 7 A schematic diagram illustrating exemplary TSN control of a transport network for a disaggregated RAN is shown;

[0105] Figure 8 A schematic diagram illustrating a high-level representation of the system architecture is shown;

[0106] Figure 9 A schematic diagram illustrating a transport network slice control device for managing NSSI through multi-layer TN control is shown;

[0107] Figure 10 shows a schematic diagram illustrating different states of TSN-NSSI;

[0108] Figure 11 A schematic diagram showing an exemplary TSN for a 5G mobile network within a local factory area;

[0109] Figure 12 A schematic diagram illustrating a service profiling process is shown;

[0110] Figure 13 A schematic diagram illustrating an exemplary process of TSN slice instance preparation and installation is shown;

[0111] Figure 14 A schematic diagram illustrating an exemplary process of TSN slice instance deletion is shown;

[0112] Figure 15 shows a schematic diagram illustrating an exemplary implementation of an interface for a hierarchical CNC single CUC;

[0113] Figure 16 A schematic diagram illustrating an exemplary implementation of an interface for a single point of control is shown;

[0114] Figure 17 A schematic diagram showing an exemplary implementation of an interface of a distributed CNC single CUC;

[0115] Figure 18 A schematic flow chart illustrating a method for a transport network slicing control device for a mobile network according to an embodiment of the present invention is provided;

[0116] Figure 19 The present invention is a flowchart diagram illustrating a method for a TSN control plane entity of a TSN-based TN according to an embodiment of the present invention. DETAILED DESCRIPTION

[0117] Figure 1 A schematic diagram of a transport network slice control device 100 according to an embodiment of the present invention is shown.

[0118] The transport network slice control device 100 includes: a first interface 101 configured to communicate with a transport network slice management entity 110 of a mobile network 1.

[0119] The transport network slice control device 100 also includes: a second interface 102, configured to interface with a TSN control plane entity 200 of the TSN-based TN 2.

[0120] The transport network slice control device 100 may include: a processing circuit ( Figure 1 (not shown in the figure), which is configured to perform, implement or initiate various operations of the transport network slice control device 100 described herein. The processing circuit may include hardware and software. The hardware may include analog circuits or digital circuits, or both analog circuits and digital circuits. The digital circuit may include components such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP) or a multi-purpose processor. In one embodiment, the processing circuit includes one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code, which, when executed by one or more processors, enables the transport network slice control device 100 to perform, implement or initiate the operations or methods described herein.

[0121] Figure 2 FIG2 is a schematic diagram showing a TSN control plane entity 200 for a TSN-based TN 2 according to an embodiment of the present invention.

[0122] The TSN control plane entity 200 is configured to: receive network slice management information delivered from the transport slice management entity 110 of the mobile network 1 through the transport network slice control device 100.

[0123] The TSN control plane entity 200 is also configured to: open the TSN-based TN 2 capability information to the network slice transmission network control device 100.

[0124] The TSN control plane entity 200 is also configured to provide TSN-based TN 2 capability information to the network slice transport network control device 100.

[0125] The TSN control plane entity 200 may include: a processing circuit ( Figure 2 The processing circuitry may include hardware and software. The hardware may include analog circuits or digital circuits, or both. The digital circuitry may include components such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), or a multi-purpose processor. In one embodiment, the processing circuitry includes one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code that, when executed by one or more processors, causes the TSN control plane entity 200 to perform, implement, or initiate the operations or methods described herein.

[0126] Figure 3 A schematic diagram of a system 300 including a transport network slice control device 100 and a TSN control plane entity 200 for a TSN-based TN 2 according to an embodiment of the present invention is shown.

[0127] For example, the system 300 may include a transport network slice control device (e.g., in conjunction with Figure 1 The transport network slice control device 100 described in conjunction with 2) and the TSN control plane entity (for example, the TSN control plane entity 200 for the TSN-based TN 2 described in conjunction with 2).

[0128] Now refer to Figure 4 , which shows a schematic diagram of a network slice management entity including a transmission slice control device 100.

[0129] The transport network slice control device 100 is exemplarily based on a transport slice multi-layer controller, which includes: a first interface 101, configured to communicate with a transport network slice management entity 110 of the mobile network 1, which is exemplarily based on NSSMF-TN.

[0130] The transport slice multi-layer controller 100 further includes: a second interface 102 configured to interface with a TSN control plane entity 200 exemplarily based on TSN domain control.

[0131] For example, IEEE TSN can provide deterministic communication based on Ethernet. A transport network slice control device 100 (eg, a transport slice multi-layer controller defined by IETF) including a first interface 101 and a second interface 102 is configured to communicate with a TSN control plane 200 .

[0132] Specifically, the first interface 101 and the second interface 102 can support network slicing and can connect the control plane of the IEEE TSN-based transport network and the transport slice multi-layer controller that communicates with the NSSMF entity of the mobile network.

[0133] Furthermore, network slicing requirements can be aligned. Furthermore, 3GPP-defined network slicing instances can be mapped to the underlying TSN transport network, taking into account the required transport network performance attributes.

[0134] In addition, the first interface 101 and the second interface 102 may be used to expose the capabilities, performance attributes and requirements of the TSN transport network to the 3GPP mobile network NSSMF entity.

[0135] In addition, the signaling part within the TSN control plane can be enhanced to enable per-tenant / slice operations. Appropriate data models can be designed, and the network slice instance state can be maintained at the transport network level to be used for mapping purposes.

[0136] The related orchestration and management actions performed by NSMF (and NSSMF) may be related to the following operations: for example, NSI (and NSSI) lifecycle management, necessary resource provisioning, instantiation configuration actions of related resources and NFs, monitoring actions, fault management and automatic repair of the underlying environment (software and hardware).

[0137] Now refer to Figure 5 , which shows a schematic diagram of an exemplary transport network illustrating a 5G mobile network.

[0138] In the transport network, the fronthaul, midhaul, and backhaul communication networks used to interconnect NFs (physical network functions (PNFs) and / or virtual network functions (VNFs)) are considered. These terms are also used as TN in [3GPP-TR38.803] and [3GPP-TR23.799] by 3GPP, [BBF TR-221], [MEF 22.2], and [ITU IMT2020 O-041].

[0139] Furthermore, in the case of a disaggregated RAN paradigm, these NFs reside in a centralized unit (CU) 502 , a distributed unit (DeDU) 503 , a remote unit (RU) 504 , and a core network (CGN) 501 .

[0140] Next, two examples of integration activities between 3GPP mobile networks and IEEE TSN-based networks will be introduced, including "Case 1: TSN for fronthaul" and "Case 2: 5G system as a logical TSN bridge."

[0141] Case 1: TSN for fronthaul: 802.1CM profile for fronthaul Based on the application area, TSN profiles have been specified to explain the standards, protocols, features, and options that should be used for a given use case. For example, existing TSN profiles are 802.1BA for AVB networks, IEC / IEEE 60802TSN profile for industrial automation, P802.1DG for automotive Ethernet communications, and IEEE 802.1CM TSN for mobile fronthaul networks. IEEE 802.1CM is the result of a joint effort between CPRI and IEEE 802.1. It describes how to meet stringent fronthaul requirements in an Ethernet-based bridging network that can support not only fronthaul services but also other concurrent service types. In 802.1CM, CPRI and eCPRI splitting is supported (Class 1 and Class 2, respectively). In both cases, the following types of data are considered:

[0142] a) User data;

[0143] b) control and manage data;

[0144] c) Synchronize data.

[0145] The CPRI specification V7.0 and the eCPRI transport network specification V1.1 define the relevant requirements (for these types of data). For example, for Class 2 (eCPRI), the maximum end-to-end one-way delay for high-priority user-plane data services between eREC and eRE is 100us. In addition, the maximum tolerable frame loss probability of control plane data is 10-6, and the internal time error of eRE / RE synchronization is required to be between 15ns and 30ns, depending on the specific situation and category. In addition to the fronthaul network, the present invention believes that TSN bridging can also be used within the 5G system to support the interconnection of different components.

[0146] Now refer to Figure 6 , which is a schematic diagram illustrating a TSN bridge 601 located outside the 5G box 502.

[0147] Case 2: 5G system as a logical TSN bridge: Based on the liaison activities between 3GPP and IEEE TSN, as described in TS23.501 clauses 4.4.8, 5.27, 5.28, Annex H, Annex I on support for TSN, and clauses 5.6.10.2, 5.7.6.3, and 5.8.2.5.3 on Ethernet forwarding; TS23.502 Annex F on support for TSN; and TS23.503 clause 6.1.3.23 on support for TSN, the 5G system 502 is considered as a logical TSN bridge, where requirements and quality of service (QoS) parameters are converted in the UPF (user plane) and AF (control plane). In this case, the network slice instance information mapping and resource allocation on the TSN side are also affected by the flow participation on a per-slice instance basis in the mobile network.

[0148] Now refer to Figure 7 , which is a schematic diagram illustrating an exemplary TSN-based transport network in a disaggregated RAN scenario.

[0149] Combine Figure 7 This paper discusses an example of a network slicing support mechanism for integrated Ethernet-based TSN for 5G. IEEE TSN technology can be applied not only to fronthaul but also to midhaul and backhaul networks. This network integration is called Xhaul.

[0150] In addition, the TSN network slicing mechanism can be applied to various transport networks (i.e., backhaul network, midhaul network, fronthaul network). In addition, one or more interfaces (e.g., the first interface 101 and the second interface 102 of the transport slice control device 100) can be provided. In addition, the mechanisms that may be required for integration between the network slicing management and orchestration system on the mobile network and the network slicing system in the TSN-based transport network are discussed.

[0151] In more detail, to support network slicing, one or more interfaces are provided between the slice-aware transport network management system and the TSN control and management plane. In principle, through this interface, TSN capabilities can be used to implement soft network slicing and hard network slicing in the transport network.

[0152] The present invention does not focus on specific TSN data plane technologies such as 802.1Qbv or 802.1Qbu, but can use any TSN data plane mechanism to provide slice isolation and performance guarantee.

[0153] For example, one or more of the following features may be supported:

[0154] Network slicing requirements can be aligned. Furthermore, 3GPP-defined network slice instances can be mapped to the underlying TSN transport network, taking into account the required transport network performance attributes.

[0155] Expose the capabilities and performance attributes and requirements of the TSN transport network to a slice-aware transport network slice controller.

[0156] Provide an appropriate data model.

[0157] Maintaining the network slice instance state at the transport network level to use it for mapping purposes.

[0158] In addition, for the control plane of IEEE TSN, there are currently three models proposed based on 802.1Qcc.

[0159] In the following, for a fully centralized scenario, the control plane of IEEE TSN is used as an example, where the TSN Centralized Network Configuration (CNC) 702 and the TSN Centralized User Configuration (CUC) 701 can be considered as those defined in IEEE TSN 802.1Qcc. The following provides a first interface 101 and a second interface 102, as well as the necessary mechanisms required to control the complete lifecycle of a TSN-based transport network slice instance. The interfaces and mechanisms can also be applied to situations where distributed protocols such as SRP and MSRP notify the CNC of flow attributes and speaker / listener requirements through the CUC.

[0160] Two specific operations can be considered for network slicing in 5G. The first operation can be to create and control a network slice instance. The second operation can be to associate a UE with a specific slice instance. For example, each QoS flow can be identified by a QoS flow identifier (QFI), and the PDU session can be managed by the SMF (based on the QFI and QoS profile of the flow provided by the Policy Control Function (PCF) on a per-slice basis).

[0161] Furthermore, the present invention is exemplarily discussed for handling the first operation, i.e., how to create and control a network slice instance on a converged TSN network, rather than the process of associating UE flows with NSSI on TSN.

[0162] Now refer to Figure 8 , which is a schematic diagram illustrating a high-level representation of the system architecture.

[0163] exist Figure 8 In the system architecture shown, the second interface 102 is exemplarily shown as a “TSN Slice Aware Interface (TSA-I)” and is provided between the TSN control plane 200 and the transport network slice controller 100 .

[0164] Furthermore, new operations within the CUC TSN management entity and the CNC TSN control entity can be supported. Figure 8The system architecture shown includes extensions to the 802.1Qdj interface and to the Yang Data Model for Transport Slice draft-wd-teas-transport-slice-yang-01 interface.

[0165] ●TSN-based transport network performance attributes and requirements are open to 3GPP mobile network capabilities.

[0166] 3GPP-defined mapping of network slice requirements from network slice instances to the underlying transport topology and link interconnections, taking into account the required transport network performance attributes.

[0167] ●Slice request / configuration / operation / decommissioning actions between the mobile network and the TSN-based transport network.

[0168] ● Maintain slice isolation on the XHAUL data plane based on TSN

[0169] ●Coordinate actions via TSN of CNC / CUC between engineering tools and transmission slice controllers.

[0170] ●Backward compatible with 5G black box methods.

[0171] The entities of the system and their functions may be as follows:

[0172] TN-NSSMF 110: TN-NSSMF is responsible for orchestrating and managing the transport network for NSSI counterparts. This entity is controlled by 3GPP.

[0173] E2e Slice-DB 803: This is assumed to be a database infrastructure that contains all NSI information. This database infrastructure is controlled by 3GPP and is used to store all information about NSI status, NSI templates, reserved resources, network functions, configurations, etc.

[0174] Transport network slice controller 100: The entity is defined in the IETF "Yang Data Model for Transport Slice draft-wd-teas-transport-slice-yang-01". This entity communicates with the TN-NSSMF to provide control and management, configuring different network control elements to deliver transport slice services. It should be noted that the control plane functions of the TN are provided by one or more domain controllers, which interface with the TN-NSSFM through the transport network slice controller. For example, different domain controllers can be used to control the fronthaul network and different domain controllers can be used to control the backhaul network. Different domain controllers can also be assigned to control different management domains. For example, one control entity can be responsible for L2 / L3 aspects, while another control entity can be responsible for topology discovery or IP configuration. From an implementation point of view, a single software solution (e.g., an SDN controller) can support all necessary functions; the domain controller can be based on SDN. The present invention defines the interface between the transport network slice controller and the TSN control / management plane.

[0175] TSN-NetSLiceDB 804: Database infrastructure containing status information for all NSSIs in the TSN TN. This database infrastructure, not controlled by 3GPP, is used to store all information related to the identification and mapping between NSIs and NSSIs, including TSN TN NSSI status, templates, reserved resources, network functions, configurations, and more. The database infrastructure is also the entity that stores TSN NSSI OAM information. For each network element or network service, considered to be each TSN TN NSSI, only specific OAM information related to that TSN TN NSSI is stored in the TN-NSDB. OAM filtering can be implemented by the domain controller, but how this is done is beyond the scope of the interface specification.

[0176] Transport network environment: Consider TN based on TSN. However, it should be noted that TSN is a Layer 2 technology that works in coordination with other technologies such as MPLS, deterministic IP / Detnet, and segment routing to deliver integrated network services.

[0177] Slice-Aware CUC 701: This is a new design of the CUC entity to achieve slice awareness. The new interface is used to update the flow information with the relevant slice identification and basically enables the communication between the slice-aware CUC / CNC and the transport network slice controller. In order to achieve backward compatibility with the 5G black box approach, the CUC initially resolves the slice-unaware flow requirements from different speakers / listeners. However, if network slicing is enabled before sending the relevant flow TSpecs to the CNC, the flow requirements will be transmitted to the transport network slice controller through the new interface to the management entity responsible for describing the slice requirements to the NSMF (e.g. CSMF). If network slicing is not enabled or all flows belong to one default network slice by default, the normal pipeline is followed and the flow information is delivered to the CNC through 802.1Qdj. The method will be explained in detail below.

[0178] TSN-NSI Templates: As part of extending the TSN CUC / CNC, TSN-NSI templates are also considered. Network slice templates are used to describe slices using the resources, services, configurations, relationships, and service function chains required by the NSI. Network slice templates define all the details required by the network orchestrator to drive all phases of the NSI lifecycle. For example, a service template is specific to a particular service and requires defining input parameters, configuration primitives, relationships / dependencies, resources and constraints, units (number of instances), machines (physical or virtual), and operational domains. Templates also include the configuration primitives required for slice instantiation and operation. For TSN networks, network slice templates can be used to define the type of NSSI, such as hard or soft slices, shared or non-shared resources, service requirements, and QoS attributes. These templates extend the GNSM Generic Network Slice Template (GST) [gsma] for TN with TSN attributes. These templates are used to compile the associated Network Slice Type (NEST) with TSN information. A Network Slice Type (NEST) is a GST with specified values. The present invention believes that the information transmitted between CSMF and NSMF should also consider the relevant TSN parameterization correction of the slice NEST.

[0179] Slice Information Library 805: The definition of such templates can be found in the Slice Information Library.

[0180] Slice-aware / tenant-aware CNC 702: In principle, the CNC receives input regarding configuration requests from the CUC 701 via a given transport protocol, input for topology discovery from network services such as LLDP, and input from users. Based on all these inputs, scheduling decisions are made for the entire network. However, according to current developments, there is no concept of tenants or slices to group different flow requests to optimize scheduling / forwarding decisions. The present invention considers that additional tenant / slice identifiers are also used for all flow requests issued by the CUC. After the CNC compiles the forwarding policy (e.g., scheduling), it is applied to the TSN bridge device through a management protocol (e.g., NETCONF, Restconf, etc.). One implementation perspective of the present invention considers that the CNC has direct access to the slice information base and the TSN-aware TN-NEST. All interfaces between the TSN control plane (200) and the transport network slice controller (100) are handled by the TSN orchestrator for message interpretation, as well as for interfaces with other TN control systems to address complexity minimization and related optimization decisions. By implementation, TSN orchestration can be implemented as an independent entity or as part of the CNC.

[0181] Now refer to Figure 9 , which is a schematic diagram illustrating a transport network slice control device 100 that manages TN-NSSI through multi-layer control.

[0182] Control actions supporting the life cycle of a TN slice instance (i.e., TN-NSSI) can be triggered by the transport network slice controller 100.

[0183] For example, for any TSN related aspects that are part of a TN-NSSI instance, the TSN control plane entity 200 is responsible for maintaining appropriate TSN functionality. It should be noted that for the entire TN, network functionality can be supported by an orchestrated control mechanism, where the CNC 702 and L2 / L3 / L4 control can tune TSN aspects and L2 / L3 / L4 aspects respectively.

[0184] In addition, there may also be an interface between the SDN controller 901 and the CNC 702 .

[0185] Now refer to Figure 10 , which is a schematic diagram illustrating different states of TSN-NSSI.

[0186] The relevant state transitions of the TSN-TN instance life cycle are described. In addition, it can be considered as the following roles, "has" relationships and processes:

[0187] ●Each tenant has a set of NSIs.

[0188] ● Each mobile network user can be associated with a set of NSIs belonging to multiple tenants.

[0189] ●PDU session establishment is the responsibility of the 3GPP control plane function. For example, according to 3GPP [TS 23.501], a specific PDU session uses a single network slice, and different PDU sessions can belong to different network slices.

[0190] ●TSN TN slice awareness identification mechanism, management aspects and processes are handled by the TSN control plane.

[0191] ●TSN-TN only provides the necessary TSN data plane to carry services per tenant / NSSI.

[0192] ● The process of mapping NSI to TN-NSSI is developed by TN-NSSMF.

[0193] The process of orchestrating (multiple) TSN TN-NSSIs is specified by the CUC-CNC. Further interactions between the CNC and the Software Defined Network (SDN) controller enable other L2, L3 / L4 control aspects, such as topology management and clock configuration.

[0194] ●The process of controlling the operation of (multiple) TSN TN-NSSIs is established by the CNC.

[0195] ● A single converged TSN network can be assumed for 5G user plane and control plane traffic, but also for non-5G related flows (e.g. PROFINET traffic over TSN in industrial environments).

[0196] The CNC is responsible for controlling TSN and non-TSN-aware flows (e.g., PROFINET).

[0197] ●Both CUC and CNC can perceive tenant slices.

[0198] The southbound CNC is unaware of slicing (according to the 802.1Qcw amendment).

[0199] The northbound CNC is slice-aware. This can be achieved by extending 802.1Qdj or by directly opening the slice-aware NSSI database to the CNC.

[0200] The interface between the transport slice controller and NSSMF (3GPP) specified by the IETF will be extended to include TSN requirements and configuration information.

[0201] ●The extension covers the capability exposure of TSN transmission network performance attributes and the requirements for 3GPP mobile networks.

[0202] ● Regarding the 3GPP network slicing architecture and the network slice instance selection and association process, the present invention is consistent with the work delivered in [TR23.799], [TS23.501] and [TS23.502] for the NextGen RAN and Core specifications, but does not limit the present invention. It should be noted that the TN control plane is not part of the NextGen Core and NextGen RAN control plane, but operates independently.

[0203] ● During the creation of an NSI, the NSMF may need to ensure that the use of the TSN TN portion of the network complies with the network slicing requirements. In order to achieve isolation between NSIs when using TSN-TN links, it is also possible to distinguish the services corresponding to different NSIs at the TSN-TN level. This can be achieved by providing NSI-specific TN parameters to each node. These TN parameters can correspond to NSI-specific IP address allocation, or L2 parameters such as VLAN tags [TR28.801-7.11], however, the present invention recognizes that this also needs to be extended to cover the TSN case. This information includes the corresponding TSN TN parameters for associating transport links.

[0204] Next, slice-specific operations that enhance the TSN control and management plane will be discussed.

[0205] Slice, resource and service identification: Identification of NSI, TN-NSSI, TN resources, TN-NF, TN interface, etc. is an important topic for the integration of NSMF and TN-NSSMF to provide end-to-end NSI.

[0206] Network Slice Identification in 3GPP: The system architecture and interfaces for the next-generation 5G RAN and Core are defined in TS 23.501 and other specifications. Furthermore, procedures in the control plane are discussed in TS 23.502 and other specifications. Identification primitives, such as NeS_ID, S-NSSAI, Tenant_ID, Temporary_ID, Token, and Tracking Area Identity (TAI), are discussed in TS 23.501 Section 5.15.2 and TS 38.300. TR 23.799 also uses some identification primitives, such as NeS_ID, S-NSSAI, Tenant_ID, Temporary_ID, Token, and Tracking Area Identity (TAI).

[0207] In addition, 3GPP has defined some identifiers required for network slicing, but has not provided data types (such an approach is used in the specification). However, the list is still not exhaustive. In addition, in the present invention, it can be intuitively considered that each component or element can have a corresponding identifier. For example, NSI has NSI_ID, NSSI has NSSI_ID, NF also has NF_ID, and so on. NSMF can use these identifiers.

[0208] For the work delivered so far, it can also be considered that the slice-aware orchestration and management system can leverage existing identifiers such as PLMN_ID, logical channel identifier, session identifier, etc.

[0209] TN identification mechanism: For the TSN network part of the TN-NSSI associated with a set of one or more NSIs, a similar identification mechanism can be assumed to exist, which can allocate (TN)NSSI_ID, etc., and can further map it to NSI_ID (provided by NSMF). This information can be stored in TSN-NetSLiceDB.

[0210] It should be noted that in the transport network slice controller, there may be technology-independent parts and technology-specific parts, for example, each part may have an identification mechanism. In this invention, two types of IDs (type A and type B) are considered, and the TSN CUC / CNC uses these two types of IDs to perceive the slice:

[0211] Category A: Identifiers related to the NSSI lifecycle.

[0212] Category B: Identifiers used for TSN network opening (e.g., node_1, link_5, pre-emption_suported, etc.).

[0213] Furthermore, it can be assumed that the identification information is generated in a native way in the TSN TN environment and is only exposed to the CUC / CNC by the transport network slice controller. Furthermore, it can be assumed that for TN-NSSI, all relevant information is stored in the TSN-NetSLiceDB, where the appropriate database table structure is used according to the data type of each element.

[0214] It should be noted that the definition of all delivered messages requires specific schema structure elements and sub-elements and their data types. For example, TSN_NSSI_ID can be represented by an integer or a uuid value. For example, the message schema definition (assuming XML format) may be as follows:

[0215] ●Case 1 (using integer ID):

[0216] <xsd:elementname="TSN_NSSI_ID"type="xsd:integer" / >

[0217] ●Case 2 (Using UUID ID): If it is UUID, first you need to define a new data type (named GUID in the example):

[0218]

[0219] NSI Isolation: The functionality required to meet TN-NSSI isolation requirements is provided by the corresponding TSN data plane mechanisms (e.g., 802.1Qbv, 802.1Qbu, 802.1Qcr, etc.). It should be noted that a TN-NNSI can be completely or partially isolated from another TN-NSSI logically and / or physically. In addition, different levels and types of isolation / separation may be required, such as slice security isolation, resource isolation, and OAM support isolation (e.g., usage and fault isolation, etc.). However, if multiple customers share the same TSN-NSSI functionality or different NSIs share the same NSSI, it is difficult to achieve management data isolation. However, it can be assumed that the CNC domain control provides and enables the necessary mechanisms for the technology-specific TSN-based TN environment to maintain slice isolation in this way.

[0220] For example, for TSN-based data plane isolation between different NSSIs, traditional technologies such as VLANs can be used to isolate services through physical or logical channels that support TN-NSSI. When slice-specific information is delivered to the CNC entity, optimized scheduling decisions can also be used to support QoS / performance guarantees on a per-slice basis.

[0221] Slice-aware TSN network orchestration: taking into account the required transport network performance attributes, adjusting network slicing requirements through interfaces (e.g., the first interface 101 and / or the second interface 102), and mapping the defined network slice instances to the underlying TSN transport topology and link interconnections.

[0222] The present invention also contemplates enhancing CUC / CNC with an orchestration mechanism that takes the following information as input:

[0223] ●TSN slice awareness information / requirements / strategies for network slicing through the interfaces defined in this invention.

[0224] ●Decisions based on flow specifications and TSN flow mapping based on active flow identification functions operating at the frame level.

[0225] ●Stream analytics by slice – dynamic processing / filtering / aggregation of sessions.

[0226] TSN can be used as a converged network where other services can be delivered simultaneously with 5G flows from other network controllers or engineering tools. For example, in industrial networks, engineering tools can describe Profinet or Modbus service requirements over TSN.

[0227] ● Service Prediction Module: Because the dynamic nature of traffic flows complicates decision-making within the CNC when applying TSN on 5G-XHAUL, a service profiling module is considered operational (rather than statically defining service requirements) to facilitate optimal decision-making. From one implementation perspective, this module can run within the CNC. From another perspective, this module can be implemented as part of the TSN orchestrator (even within the CUC), but it can also be independent and exposed as a service within the CUC / CNC.

[0228] Now refer to Figure 11 , which is a schematic diagram illustrating an exemplary TSN of a 5G mobile network within a local area of ​​a factory.

[0229] TSpec Delivery and the Role of the CUC / CNC in the Process: TS23.501 describes a black-box approach for integrating TSN with 5G systems, where operations within the 5G system are independent of those within the TSN control plane. For example, communication between the two systems can be performed through the interaction between the TSN CNC and the AF-TT, where a translation service can deliver TSN flow requirements to the 5G system. The flow requirements are delivered from the CNC to the 5G system, which acts as a transparent TSN bridge. The relevant resources are then allocated within the 5G system to support the required QoS for these TSN flows.

[0230] However, in the present invention, a traffic profiling mechanism is introduced, because in the case of network slicing, resource allocation is done proactively and does not need to be on a per-flow basis. This means that network slices are provided a priori with full or partial knowledge of the exact flows that may traverse the TSN network. Figure 12 The illustrated process discusses an example of service profiling.

[0231] Now refer to Figure 12 , which is a schematic diagram illustrating the service profiling process.

[0232] • Step 1: Following the black box approach, CUC 701 is collecting streaming requirements from TSN talkers and listeners.

[0233] • Step 2: Information is not only delivered from CUC 701 to CNC 702 (normal process), but is also used to contract TSN-aware GST / NEST.

[0234] ● Step 3: After TSN senses that NEST is ready, CSMF is contracting the entire network slice request. It should be noted that it is considered that on the TSN network, not only time-critical services will be delivered on the TSN network (not just the services initially announced by CUC 701), but TSN can be used to support any type of L2 TSN connection.

[0235] ●Step 4: After preparing the e2e slice definition, CSMF triggers a request for the e2e slice to NSMF.

[0236] • Step 5: NSMF calls necessary counterparts (RAN NSSMF, Core NSSMF, TN NSSMF) to request resources that meet the QoS and flow requirements described in NEST.

[0237] ●Step 6: For the TN part, the TN-NSSMF calls the transport network slice controller 100, which is responsible for all control aspects on a per-slice basis.

[0238] ●Step 7: The transport network slice controller 100 transmits the now slice-aware flow definition together with the additional flows specified in NEST back to the CUC 701 and will traverse the TSN network.

[0239] ● Step 8: Update the relevant database with the new slice-aware identifier. At this point, service profiling can also be performed in service modeling and regression analysis to provide future service loads before scheduling decisions.

[0240] ●Step 9: New slice-aware requirements are delivered to CNC 702.

[0241] ●Step 10: The transport network slice controller 100 also interacts with the CNC to perform other parameterizations required for TSN network tuning.

[0242] • Step 11: The CNC 702 performs the best decision and configures the TSN bridge accordingly.

[0243] For runtime operations, the control loop can be the same, but without steps 1 to 3. Depending on the runtime operation (new node, flow entering the network, flow leaving the network, etc.), the definition of NEST will be adjusted accordingly, and resource reconfiguration may also occur. It should be noted that this design maintains backward compatibility with network slicing unawareness because (for example) the CNC 702 still interacts with the AF when attaching flows for QoS provisioning and mapping processes. To trigger network slicing awareness, a simple ON / OFF module can be run within the TSN control plane.

[0244] Next, descriptions and specifications of the interfaces (first interface 101 and second interface 102) are given.

[0245] TSN slice-aware interface: A vendor-neutral representation can be assumed for configuration and interaction with TSN TN network elements (i.e., routers and switches). For example, OpenConfig uses the YANG language [RFC 6020] to provide a vendor-neutral model for element configuration and operational status. For transport protocols or serialization, three potential candidates are: a) NETCONF over SSH using XML encoding; b) RESTCONF over https using, for example, JSON representation; and c) gRPC: Google's open source protobuf using RPC over HTTP. The SDN control plane can be used to implement (multiple) TN domain controllers in a variety of implementation scenarios.

[0246] Description: For example, the description could be whether the interface is used for all communications between the TSN CUC / CNC control and orchestration system and the transport network slice controller 100 of the slice-aware transport network?

[0247] For example, the interface can be used for all message transmission to support TSN functions throughout the entire life cycle of TN-NSSI, and can also be used for capability exposure of TSN TN.

[0248] Stakeholders: The interface may be used by transport network builders and 3GPP system integrators. This can enable third parties such as enterprises, service providers, or content providers to efficiently operate network slices on converged TSN networks.

[0249] Requirements: The TN-NSSMF entity and the transport network slice controller are operational, and a communication channel is established between the controller and the TSN-CUC / CNC.

[0250] Communication protocol, connection establishment, maintenance, termination: The transport network slice controller 100 application requires multiple pre-configured parameters (e.g., IP address and port and the transport protocol to be used (e.g., TLS or TCP) to initiate a connection with the CUC / CNC. If the CUC 701 opens a REST interface, communication can be carried out via https.

[0251] For initial connection establishment, connection-specific messages need to be exchanged for maintenance and termination. For the initial version of the interface, it can be assumed that the relevant protocols can operate via synchronous point-to-point communication. However, all possible communication modes can be considered, such as publish / subscribe, multipoint-to-multipoint communication, synchronous, asynchronous, etc. In addition, regarding authentication and encryption, TLS / SSL cryptography can be used to protect data integrity in the transport channel. Regarding authorization, it can be assumed that this is handled by the transport network slice controller function.

[0252] For all necessary communication modes, an event-driven mechanism can be assumed, where events are generated in two ways: a) automatically (periodically or aperiodically); b) on-demand. Each event can generate a message that is sent over the slice-aware TSN interface.

[0253] Issues such as message segmentation and reassembly, acknowledgment, packet errors, flow control, and routing are handled by the lower layers of the protocol stack. There is no specific tunneling requirement, and the initial interface protocol stack utilizes only TCP / IP.

[0254] For the first version of the interface, there may be no priority defined for a particular NSSI and all requests are handled by the CNC on a first-come, first-served basis.

[0255] Message Specification: This invention identifies the following message categories for information exchange between the transport network slice controller and the TSN control plane:

[0256]

[0257] The exemplary processes of TSN slice preparation and installation and TSN slice deletion are as follows: Figure 13 and Figure 14 shown.

[0258] Exemplary design options for implementing the interface are discussed.

[0259] Examples of design options for implementing hierarchical CNC interfaces include Figure 15 Another example of a design option for implementing an interface for a single CUC / CNC control is shown in Figure 16 Another design option for implementing a distributed CNC interface is shown in Figure 17 shown.

[0260] The embodiments may be based on TSN network convergence in factory workshops, including 5G slicing, Profinet, etc.

[0261] In addition, end-to-end performance may be affected by intra-class interference. In addition, according to the present invention: TSN is updated according to each TN slice update and other industrial network requirements. In addition, as described above, new interface processes can also be designed.

[0262] Embodiments may be based on inter-slice migration.

[0263] For example, existing 3GPP standard procedures only enable users to change (or switch) slices and lack a formal mechanism for session continuation between slices. Therefore, enhancements are needed to enable seamless inter-slice migration or handover. Because TSN QoS / scheduling can be targeted to specific slice-talker / listener pairs, end-to-end performance is affected by inter-slice mobility.

[0264] According to the present invention, TSN is updated according to each TSN slice update and each user slice participation update. In addition, as described above, a new interface process can also be designed.

[0265] In one embodiment, a message specification for transmitting a network slice request may be provided.

[0266] For example, the following message specification illustrates how to define a network slice request.

[0267] Services provided: Network slicing request for TSN TN resources

[0268] Preconditions: Conditions that must be met before a service can be called.

[0269] o CUC / CNC are operational to support TSN domain control mechanisms.

[0270] o The communication channel between the CNC and the transport network slice controller is operational.

[0271] o TSN-NSDB stores all status information of all TSN-TN-NSSIs.

[0272] o TSN-NSDB stores all resource reservations of all TSN-TN-NSSIs.

[0273] o TN-NSSI creation / activation / deactivation / termination operation is not in progress

[0274] Postcondition

[0275] oA new TN-NSSI is created.

[0276] oNSMF has been notified

[0277] o TSN data plane supports NSSI connection

[0278] The message schema in xsd format might be as follows:

[0279]

[0280] Figure 18 The method 1800 of the transport network slice control device 100 of the mobile network 1 according to one embodiment of the present invention is shown. As described above, the method 1800 can be performed by the transport network slice control device 100.

[0281] Method 1800 includes step 1801: communicating with the transport network slice management entity 110 of the mobile network 1 via the first interface 101.

[0282] The method 1800 further comprises step 1802 : communicating with a TSN control plane entity 200 of the TSN-based TN 2 via the second interface 102 .

[0283] Figure 19 A method 1900 of a TSN control plane entity 200 for a TSN-based TN 2 according to an embodiment of the present invention is shown.

[0284] Method 1900 also includes step 1901: receiving network slice management information delivered from the transport slice management entity 110 of the mobile network 1 through the transport network slice control device 100.

[0285] Method 1900 also includes step 1902: opening the configuration information of TSN-based TN 2 to the network slice transmission network control device 100.

[0286] Method 1900 also includes step 1903: providing TSN-based TN 2 capability information to the network slice transmission network control device 100.

[0287] The present application has been described with reference to various embodiments and implementations as examples. However, those skilled in the art will be able to understand and implement other variations in practicing the claimed invention, based on a study of the drawings, the present disclosure and the appended claims. In the claims and the specification, the word "comprising" does not exclude other elements or steps, and "a" does not exclude a plurality. A single element or other unit may fulfil the functions of several entities or items described in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not mean that a combination of these measures cannot be used effectively.

Claims

1. A transport network slice control device (100), the transport network slice control device (100) comprising: A first interface (101) configured to communicate with a transport network slice management entity (110) of a mobile network (1) and to expose capability information of a transport network TN (2) based on a time sensitive network TSN to the mobile network; The second interface (102) is configured to: Obtaining the capability information of the TSN-based transport network TN (2) from a TSN control plane entity (200) of the TSN-based transport network TN (2); as well as Determined TN performance attributes are provided to the TSN-based TN (2).

2. The transport network slice control device (100) according to claim 1, further configured to: sending network slice control and management information to the transport network slice management entity (110) of the mobile network (1) via the first interface (101), or receiving the network slice control and management information from the transport network slice management entity (110); and / or Sending network slice control and management information required by the TSN-based TN (2) to the TSN control plane entity (200) via the second interface (102), or receiving the network slice control and management information required by the TSN-based TN (2) from the TSN control plane entity (200).

3. The transport network slice control device (100) according to claim 2, wherein: The network slice control and management information includes one or more of the following: - TSN-TN network slicing requirements information; - TSN-TN slice instance creation request; - TSN-TN slice instance creation response; - TSN-TN slice instance status information; - TSN-TN slice instance strategy information; - TSN-TN slice instance configuration information; - TSN-TN slice instance operation actions; - TSN-TN slice instance deactivation action; - Soft TSN slicing instance capability; - Hard TSN slicing instance capability.

4. The transport network slice control device (100) according to claim 1, further configured to: receiving updated TN slice information or updated TN slice resource allocation from the transport network slice management entity (110) of the mobile network (1) via the first interface (101); and / or The updated TN slice information or the updated TN slice resource allocation is sent to the TSN control plane entity (200) via the second interface (102).

5. The transport network slice control device (100) according to claim 1, further configured to: receiving a TN slice isolation requirement from the transport network slice management entity (110) of the mobile network (1); and Maintain TN slice isolation on the TSN-based data plane according to the received TN slice isolation requirement.

6. A TSN control plane entity (200) for a transport network TN (2) based on a time-sensitive network TSN, the TSN control plane entity (200) comprising a processing circuit, and the processing circuit being configured to: receiving, through the transport network slice control device (100), network slice control and management information delivered from a transport network slice management entity (110) of the mobile network (1); Opening capability information of the TSN-based TN (2) to the transport network slice control device (100); Providing the capability information of the TSN-based TN (2) to the transport network slice control device (100); Obtaining determined TN performance attributes from the transport network slice control device (100); as well as Based on the determined TN performance attributes, network slice control and management information received from the transport network slice management entity (110) of the mobile network (1) is mapped to TSN specific performance attributes of the TSN based TN (2) on a per network slice basis.

7. The TSN control plane entity (200) according to claim 6, wherein the processing circuit is further configured to: Storing the information in a network slice database; and Expose information related to the lifecycle of one or more transport network slice instances to Centralized User Configuration (CUC) or Centralized Network Configuration (CNC).

8. The TSN control plane entity (200) according to claim 6 or 7, wherein: The network slice control and management information includes one or more of the following: - TSN-TN network slicing requirements information; - TSN-TN slice instance creation request; - TSN-TN slice instance creation response; - TSN-TN slice instance status information; - TSN-TN slice instance strategy information; - TSN-TN slice instance configuration information; - TSN-TN slice instance operation actions; - TSN-TN slice instance deactivation action; - Soft TSN slicing instance capability; - Hard TSN slicing instance capability.

9. The TSN control plane entity (200) according to claim 6, wherein the processing circuit is further configured to: receiving, from the transport network slice control device (100), a TN slice isolation requirement received from the transport network slice management entity (110) of the mobile network (1); and Maintain TN slice isolation on the TSN-based data plane according to the received TN slice isolation requirement.

10. The TSN control plane entity (200) according to claim 6, which is based on a network slice-aware TSN control plane entity, the network slice-aware TSN control plane entity comprising: A centralized network configuration CNC (702) configured to control a TSN TN network slice subnet instance NSSI; or A centralized user configuration CUC (701) is configured to deliver TSN TN-NSSI flow specification requirements to the CNC (702).

11. The TSN control plane entity (200) according to claim 10, wherein: The CNC is further configured to control TSN slice-aware operations and / or TSN non-TSN slice-aware operations.

12. The TSN control plane entity (200) according to claim 6, comprising a network slice database, wherein the network slice database is configured to: Resource allocation information and / or resource identification and mapping information regarding flow performance attributes is stored for each TN NSSI.

13. A system (300) for communication, comprising: At least one transport network slice control device (100) for a mobile network (1) according to any one of claims 1 to 5; as well as At least one TSN control plane entity (200) for a transport network TN (2) based on a time sensitive network TSN according to any of claims 6 to 12.

14. A method (1800) for a transport network slice control device (100) for a mobile network (1), the method (1800) comprising: Communicating (1801) with a transport network slice management entity (110) of a mobile network (1) via a first interface (101), and opening capability information of a transport network TN (2) based on a time-sensitive network TSN to the mobile network; Via the second interface (102): Obtaining the capability information of the TSN-based transport network TN (2) from a TSN control plane entity (200) of the TSN-based transport network TN (2); as well as Determined TN performance attributes are provided to the TSN-based TN (2).

15. A method (1900) for a TSN control plane entity (200) of a transport network TN (2) based on a time-sensitive network TSN, the method (1900) comprising: receiving (1901) network slice control and management information delivered from a transport network slice management entity (110) of a mobile network (1) through a transport network slice control device (100); Opening (1902) capability information of the TSN-based TN (2) to the transport network slice control device (100); as well as Providing (1903) the capability information of the TSN-based TN (2) to the transport network slice control device (100); Obtaining determined TN performance attributes from the transport network slice control device (100); as well as Based on the determined TN performance attributes, network slice control and management information received from the transport network slice management entity (110) of the mobile network (1) is mapped to TSN specific performance attributes of the TSN based TN (2) on a per network slice basis.

16. A computer program product comprising instructions which, when the program is executed by a computer, cause the computer to perform the steps of the method (1800) according to claim 14 or the method (1900) according to claim 15 to be performed.

Images