Multi-access edge computing (MEC) control and resource characterization
By configuring the 5G system as multiple TSN blocks and adopting distributed configuration modules, the problem of insufficient flexibility in data transmission paths in integrated TSN-5G systems is solved, the system flexibility and reliability are improved, and heterogeneous network environments are supported scheduling and configuration.
Patent Information
- Application Number
- CN202380029075.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-04
- Filing Date
- 2023-03-06
- Publication Date
- 2024-11-05
AI Technical Summary
In the existing integrated TSN-5G system, the 5G system is configured as a single TSN component, limiting the flexibility of data transmission paths for some components of the 5G system, resulting in an increase in the possibility of data delays and errors, and the inability to effectively support decentralized TSNs. Configure the model.
Configure the 5G system into multiple discrete TSN blocks, each TSN block is configured according to the TSN specification, and uses a distributed configuration module to replace the centralized configuration controller, supports the interconnection of multiple topology structures, and exchanges configuration data through standardized APIs to achieve Flexible data flow management.
It realizes flexible configuration of data transmission paths of some components of the 5G system, reduces the risk of data delay and error, improves the flexibility and reliability of the system, and supports scheduling and configuration in a heterogeneous network environment of multiple vendors.
Smart Images

Figure CN118901253A_ABST
Abstract
Description
[0001] priority
[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 316,808, filed on March 4, 2022, which is incorporated herein by reference in its entirety. Technical Field
[0003] The present description relates generally to the integration of wireless communication systems and time-sensitive networks (TSNs), and more particularly, for example, to multiple components of wireless communication systems configured as TSNs. Background Art
[0004] Some applications, such as industrial automation and manufacturing, require ubiquitous and seamless connectivity with strict deterministic timing requirements for communication between various devices or components of the application (e.g., industrial controllers, sensors, actuators, etc.). To meet such requirements, a technical term related to deterministic networks - TSN systems, which provide deterministic communications with relatively strict quality of service (QoS) parameters, such as latency, jitter, and reliability requirements for data services, can be integrated with 5G wireless communication systems, which provide high-reliability services, such as ultra-reliable low-latency communication (URLLC) services. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Certain features of the inventive technology are set forth in the appended claims. However, for purposes of illustration, several aspects of the inventive technology are set forth in the following drawings.
[0006] Figure 1 An example of a conventional integrated TSN-5G system 100 is shown according to one or more embodiments.
[0007] Figure 2 A block diagram of an example integrated TSN-5G system 200 architecture is shown according to one or more embodiments.
[0008] Figure 3 Corresponding elements of the integrated TSN-5G system 100 and the integrated TSN-5G system 200 are shown according to one or more embodiments.
[0009] Figure 4 A block diagram of an example TSN block is shown according to one or more embodiments.
[0010] Figure 5 An example parameter set for an example TSN block is shown according to one or more embodiments.
[0011] Fig. 6A , 6BA block diagram illustrating an example integrated TSN-5G system architecture including MEC (a type of edge-enabled device) according to one or more embodiments.
[0012] Figure 7 An electronic system is shown with which one or more embodiments of the present technology may be implemented.
[0013] Figure 8 A block diagram of an example integrated TSN-5G system 800 architecture is shown in accordance with one or more embodiments.
[0014] Fig. 9 A 5G system including a TSN block representing or corresponding to a MEC module is shown.
[0015] Fig.10 Improved schemes for implementing MEC in 5G networks according to some embodiments are shown.
[0016] Fig.11 A communication system for implementing an improved scheme for implementing MEC in a 5G network according to some embodiments is shown. DETAILED DESCRIPTION
[0017] The detailed description set forth below is intended to describe various configurations of the technology of the present invention, and is not intended to represent the only configuration in which the technology of the present invention can be practiced. The accompanying drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for providing a thorough understanding of the subject technology. However, the technology of the present invention is not limited to the specific details set forth herein and can be practiced using one or more other embodiments. In one or more embodiments, structures and components are shown in block diagram form to avoid blurring the concept of the technology of the present invention.
[0018] As mentioned above, for some applications such as, but not limited to, industrial automation, manufacturing, and communications within aviation and automotive vehicles, TSN systems that provide deterministic communications can be integrated with fifth-generation (5G) wireless communication systems, which provides flexibility and ultra-reliable low-latency communication (URLLC) services. However, typically in such integrated TSN-5G systems, the entire 5G system is configured to operate as a single TSN component (e.g., a TSN bridge), and the integrated system is configured to be a fully centralized configuration model, such as using one centralized TSN configuration controller. Therefore, this integrated system may not support the flexibility of deploying a 5G system that includes various components of a decentralized TSN configuration provided by different vendors or used for the integrated system. In addition, the 5G system can support reliable communications by using redundant paths for data transmission. However, in the case where the 5G system is configured as a TSN component in a typical TSN-5G integrated system, the redundant path is configured across the entire 5G system through all its components (e.g., from the user equipment (UE) to the user plane function (UPF)). This does not allow the flexibility to set up redundant data transmission paths for only part of the 5G system, such as parts of the 5G system that are more susceptible to data delays and / or errors (e.g., the air interface between the UE and the Radio Access Network (RAN) / gNodeB).
[0019] In order to solve the above-mentioned problems in the integrated TSN-5G system, the technology of the present invention provides a novel architecture, in which instead of being configured as a single TSN component or block, the 5G system is configured as a set of discrete 5G components, each of which is configured as a discrete TSN block. In other words, the present disclosure provides an architecture in which the 5G system in the integrated TSN-5G system is divided into multiple TSN blocks, each of which is configured according to the TSN specification (e.g., in accordance with IEEE 802.1Q and related standards), such as as a TSN bridge, a TSN terminal device, or a combination of both. In addition, instead of having a centralized configuration controller that controls the TSN-5G system, the technology of the present invention provides multiple distributed configuration modules in the TSN-5G system. The configuration modules can be interconnected in one or more topologies (including mesh, star, tree, or random), and each configuration module can be responsible for communicating with one or more TSN blocks and configuring one or more TSN blocks.
[0020] As discussed in more detail below, each of the multiple TSN blocks of the 5G system includes a parameter set that describes the ability to support and execute a data flow (e.g., carrying URLLC data services) through the TSN block. In addition, each TSN block may include at least one configuration interface configured to support the interaction of the TSN block with its corresponding configuration module. The configuration interface can be used to provide the parameter set of the TSN block to the corresponding configuration module, and receive configuration data (e.g., transmission schedule, data flow identification, regulatory rules, etc.) from the configuration module to support one or more data flows through the TSN block. Each TSN block can be configured to execute or operate according to the configuration data (received via the configuration interface), and transmit the data in each data flow according to the specifications provided in the configuration data. Finally, each TSN block may also include a monitoring and diagnostic module, which is configured to monitor the runtime behavior of the TSN block and report the behavior through the configuration interface or via a separate interface of the TSN block.
[0021] Each of the plurality of distributed configuration modules may be an external facility responsible for configuring one or more TSN blocks, or may be configured as a software module within a TSN block that only configures the TSN block. Each configuration module may be configured to determine configuration data and provide the configuration data to the TSN block controlled by the configuration module, the configuration data including a TSN schedule for one or more data streams to be transmitted through the TSN block. The configuration modules may exchange information with each other using a standardized application programming interface (API). The exchanged information may include information about the cycle time of the TSN system (e.g., supported administrator cycle time (ACT), discrete levels including ACT buckets each corresponding to a specific data stream, maximum / minimum cycle time), configuration data including a transmission schedule for one or more TSN blocks (including time offset / duration / resources for transmission), and information for requesting or responding to a request for resource allocation. In some embodiments, one or more of the plurality of configuration modules may be adapted as a "controller" or "controller module", which may include components configured or adapted to provide instructions, control, operation, or any form of communication to an operable component to affect its operation. The controller module may include any known processor, microcontroller or logic device, including but not limited to: a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a full authority digital engine control (FADEC), an aviation system, a proportional controller (P), a proportional integral controller (PI), a proportional differential controller (PD), a proportional integral differential controller (PID controller), a hard-wired logic controller (e.g., for encoding, decoding, transcoding), etc. or a combination thereof.
[0022] 3GPP Release 8 classifies self-organizing networks (SON) into three main categories: self-configuration, self-optimization, and self-healing. Self-organization is considered to be a mechanism or process that enables a system or network to change its organization during its execution time without explicit commands. Self-configuration is defined as a process that requires minimal operator intervention to incorporate a new network element (NE) into service, where a network element is a manageable logical entity that incorporates one or more physical devices. In some embodiments, a TSN block (discussed below) may be self-configured and incorporated into a 5G system as a NE with minimal human intervention. This can be achieved by TSN applications that automatically share their TSN flow (stream) characteristics and latency requirements with the TSN block. TSN blocks can collaborate to share flow characteristics and determine a feasible TSN schedule.
[0023] Figure 1 A non-limiting example of a conventional integrated TSN-5G system 100 is shown, wherein a 5G system 106 is configured to simulate a single TSN component (e.g., a TSN bridge). In general, the system 100 is configured as a deterministic TSN system to transmit data between end devices, such as input / output (I / O) devices 102 and controllers 104, via a 5G system 106 (simulated as a TSN bridge) and one or more (conventional) TSN bridges 108 and using a TSN controller 110. The system 100 is configured based on standard methods for time synchronization and traffic management, thereby allowing deterministic communication between end devices, such as I / O devices 102 and controllers 104, over a standard Ethernet network. For example, the system 100 may operate in accordance with the IEEE 802.1QTSN specification suite, which standardizes layer 2 communications for networking protocols that provide deterministic communication while sharing the same infrastructure. For example, many standards establish various technical paradigms for TSN system clock synchronization (802.1AS, Generalized Precision Time Protocol (gPTP)), frame preemption (802.3br and 802.1Qbu), scheduled traffic (802.1Qbv), and redundancy management (Frame Replication and Elimination for Reliability (FRER) IEEE 802.1CB). These standards must work together at Ethernet Layer 2 to ensure that critical control and safety functions are executed while meeting their respective deadlines and constraints. As another embodiment, a similar integrated system can be configured to implement TSN technology over a wireless local area network (wireless LAN), such as a Wi-Fi network, for example, based on Wi-Fi 6 and other common wireless LANs.
[0024] For example, the 802.1Qbv TSN standard provides for scheduled transmission of safety-critical data frames in a predetermined manner and is incorporated herein by reference in its entirety. As used herein, "TSN architecture" may refer to, but is not limited to, networks, components, elements, units, nodes, hubs, switches, controls, modules, paths, data, data frames, services, protocols, operations, transmissions, and combinations thereof that are attached to, configured for, or comply with one or more of the IEEE 802.1TSN standards. The 802.1QbvTSN standard addresses the transmission of critical and non-critical data services within TSN. Critical data services are guaranteed to be delivered at scheduled times, while non-critical data services are generally given lower priority. Various service classes have been established according to IEEE 802.1Q for prioritizing different types of data services.
[0025] Ethernet frame preemption is defined by the IEEE 802.3br and IEEE 802.1Qbu standards, which can suspend the transmission of non-critical Ethernet frames and are also conducive to reducing the latency and latency variation of critical services. The resource management foundation is defined by the TSN configuration model (IEEE 802.1Qcc). Centralized network configuration (CNC) 112 can be applied to network devices (bridges, such as 5G system bridges 106, bridges 108), and centralized user configuration (CUC) 114 can be applied to user devices (terminal stations, such as I / O devices 102). The fully centralized configuration model follows the software defined networking (SDN) approach. In other words, the CNC 112 and CUC 114 in the controller 110 provide a control plane instead of a distributed protocol. In contrast, a distributed control protocol is applied in a fully distributed model, in which there is no CNC or CUC.
[0026] Due to ultra-reliability, high availability can be provided for data streams through frame replication and elimination (FRER) for reliability (IEEE 802.1CB) through per-packet level reliability mechanisms. This provides reliability by transmitting multiple copies of the same data packet on disjoint paths in the network. Per-stream filtering and policy formulation (802.1Qci) improves reliability by preventing bandwidth violations, failures, and malicious behavior. In addition, time synchronization in TSN systems can be defined by the generalized precision time protocol (gPTP) (802.1AS), which is a profile of the precision time protocol standard (IEEE 1588). gPTP provides reliable time synchronization, which can be used by other TSN tools, such as scheduled services (802.1Qbv).
[0027] In order to achieve the required level of reliability, TSN employs time synchronization and time-aware data traffic shaping. Data traffic shaping uses a schedule to control the gating of transmissions on network switches and bridges (e.g., nodes). In some aspects, the schedule for such data traffic in TSN can be determined before the operation of the network. In other aspects, the schedule for data traffic can be determined during the initial design phase based on system requirements and updated as needed. For example, in addition to defining the TSN topology (including communication paths, bandwidth reservations, and various other parameters), network-wide synchronization times for data transmission can also be predefined. This plan for data transmission on the communication path of the network is generally referred to as a "communication schedule" or simply a "schedule." A schedule for data traffic on TSN can be determined for a specific data packet on a specific path, at a specific time, and for a specific duration. A non-limiting example of a technique for generating a schedule for TSN data traffic is discussed in U.S. Application No. 17 / 100,356, which is incorporated herein by reference in its entirety.
[0028] Time-critical communications between terminal devices or nodes in TSN (e.g., I / O devices 102 and controllers 104) include "TSN flows", also referred to as "data flows" or simply "flows". For example, a data flow may include datagrams, such as data packets or data frames. Each data flow is unidirectional, from a first originating or source terminal device in the system (e.g., I / O device 102) to a second destination terminal device (e.g., controller 104), with a unique identification and time requirements. These source devices and destination devices are generally referred to as "speakers" and "listeners". Specifically, "speakers" and "listeners" are the source and destination of a data flow, respectively, and each data flow is uniquely identified by a terminal device operating in the system. It should be understood that for a given network topology including multiple interconnected devices, a set of data flows between interconnected devices or nodes can be defined. For example, a set of data flows can be between interconnected devices. For a set of data flows, various subsets or arrangements of data flows can be additionally defined. Furthermore, time-critical communications between end devices or nodes in a TSN include "TSN streams" or "streams," where each TSN stream may originate at a particular talker node intended to communicate to one or more listener nodes. Thus, each TSN stream may include one or more data streams, where each data stream is between a talker node (from which the TSN stream originates) and a listener node.
[0029] Both the end devices (e.g., 102, 104) and the switches (often referred to as "bridges" or "switching nodes") (e.g., 106, 108) transmit and receive data (in one non-limiting example, Ethernet frames) in a data stream based on a predetermined schedule. The switching nodes and the end devices must be time synchronized to ensure that the predetermined schedule for the data stream is correctly followed throughout the network. For example, in Figure 1 In the embodiment, clock 116 indicates that various switching nodes and terminal devices (including 5G system 106) in TSN system 100 are time synchronized with reference to a global clock (the highest level clock timing). In some other aspects, only switches can transmit data based on a predetermined schedule, while terminal devices such as traditional devices can transmit data in an unscheduled manner.
[0030] Data flows within a TSN may be scheduled using a single device (e.g., controller 110) that assumes a fixed path through the network between speaker / listener devices and switching nodes in the network. Alternatively, a collection of devices or modules may be used to schedule data flows. Whether a single device or a collection of devices, the scheduling device may be arranged to define a centralized scheduler. In yet other aspects, the scheduler device may include a distributed arrangement. The TSN may also receive non-time sensitive communications, such as rate-limited communications. In one non-limiting example, the scheduling device may include an offline scheduling system or module.
[0031] A variety of mechanisms may be used to mark TSN traffic, including VLAN tags Ethernet addresses IP header information, and combinations of VLAN tags Ethernet addresses and IP header information. Traffic may be identified and marked anywhere in the system before protocol data unit (PDU) identification is required. TSN speakers may create multiple TSN streams (streams) with different TSN latency and determinism requirements, and may be assigned different paths to meet the requirements. In some embodiments of the invention, latency and determinism values may be specified and provided to TSN applications as a finite set of static discrete values, rather than being provided with an infinite set of continuous values.
[0032] In some embodiments, in various aspects, the I / O terminal device 102 can be a complex mechanical entity, such as a production line in a factory, a gas power plant, an avionics data bus on an aircraft, a jet engine on one aircraft in a fleet (e.g., two or more aircraft), a digital backbone in an aircraft, an avionics system, a mission or flight network, a wind farm, a locomotive, etc. In various embodiments, the I / O terminal device 102 can include any number of terminal devices, such as sensors, actuators, motors, and software applications. The sensor can include any conventional sensor or transducer, such as a camera that generates video or image data, an x-ray detector, an acoustic pickup device, a tachometer, a global positioning system receiver, a wireless device that transmits a wireless signal and detects reflections of the wireless signal to generate image data, or another device.
[0033] In addition, actuators (e.g., devices, equipment, or machines that move to perform one or more operations of the I / O device 102) can communicate using the TSN system 100. Non-limiting examples of actuators can include brakes, throttles, robotic devices, medical imaging devices, lights, turbines, etc. The actuator can transmit state data of the actuator to one or more other devices (e.g., to other I / O devices 102, controllers 104 via the TSN system 100). The state data can represent the position, state, operating condition, or the like of the actuator sending the state data. The actuator can receive command data from one or more other devices of the TSN system 100 (e.g., other I / O devices 102, controllers 104). The command data can represent instructions for how or when to cause the actuator to move, operate, etc.
[0034] In some embodiments, the controller 104 may communicate various data between or among the I / O terminal devices 102 via the TSN 100. For example, the control system 104 may communicate command data to one or more of the devices 102, or receive data, such as status data or sensor data, from one or more of the devices 102. Thus, the controller 104 may be configured to control the operation of the I / O devices 102 based on data obtained or generated by or communicated among the I / O devices 102 to allow, for example, automated control of the I / O devices 102 and to provide information to operators or users of the I / O devices 102. The controller 104 may define or determine data flows and data flow characteristics in the TSN system 100.
[0035] Referring now to the 5G system 106 within the system 100, the 5G system 106 is a wireless communication system for carrying TSN traffic between various TSN terminal devices, such as the I / O device 102 and the controller 104. In some implementations, the 5G system 106 is configured to emulate one TSN bridge per user plane function (UPF) (similar to the TSN bridge 108, according to the TSN standards discussed above). The 5G system 106 may be a new radio (NR) network implemented according to the 3GPP 23 and 38 series of specifications (incorporated herein in their entirety) and integrated into the system 100 according to the 3GPP Release 17 23.501 standard v17.1.1 and v17.2.0 (incorporated herein in their entirety). As shown, the 5G system 106 may include a user equipment (UE) 118, a RAN (gNB) 120, a user plane function (UPF) 122 in the 5G user plane, and an application function (AF) 124 and a policy control function (PCF) 126 in the 5G control plane, as well as other components. In some embodiments, the 5G system 106 may be configured to provide ultra-reliable low-latency communication (URLLC) services. The 5G system 106 based on the new air interface (NR) interface includes several functionalities to achieve low latency for selected data streams. NR enables shorter time slots in radio subframes, which is beneficial for low-latency applications. NR also introduces micro-time slots, in which prioritized transmissions can be started without waiting for time slot boundaries, thereby further reducing latency. As part of giving priority and faster radio access to URLLC services, NR introduces preemption, in which URLLC data transmissions can preempt ongoing non-URLLC transmissions. In addition, NR applies extremely fast processing to achieve retransmissions even within short latency limits.
[0036] In some embodiments, 5G defines an ultra-robust transmission mode for increased reliability of both data and control radio channels. Reliability is further improved by various techniques, such as multi-antenna transmission based on multiple-input multiple-output (MIMO) technology, use of multiple carriers, and packet replication on independent radio links.
[0037] Time synchronization is embedded in the 5G cellular radio system as a fundamental part of its operation, which is already a common practice in early cellular networks. The radio network components themselves are also time synchronized, for example, through the precision time protocol telecommunication profile. This provides a good basis for providing synchronization for time-critical applications. For URLLC services, the 5G system 106 uses time synchronization for its own operation, as well as multiple antennas and radio channels that provide reliability. In addition to the 5G RAN features, the 5G system 106 can also provide solutions in the core network (CN) for Ethernet networking and URLLC. 5G CN supports native Ethernet protocol data unit (PDU) sessions. 5G assists in establishing redundant user plane paths through 5GS including RAN, CN and transport networks. 5GS also allows redundant user planes between RAN and CN nodes and between UE and RAN nodes separately.
[0038] As mentioned above, in the integrated system 100, the 5G system 106 has one TSN (virtual) bridge per UPF. The 5G system 106 includes TSN transformer (TT) functionality for adapting the 5G system 106 to the TSN domain for the user plane and the control plane, thereby hiding the internal procedures of the 5G system 106 from the TSN bridge network. The 5G system 106 provides TSN bridge ingress and egress port operations through the TT functionality. For example, the TT supports hold and forward functionality for de-jittering. Figure 1 The situation is shown when the 5G system 106 connects the end station 102 to the bridge network 108; however, the 5G system 106 can also interconnect the bridges 108.
[0039] For the 5G system 106 to be integrated into the TSN system 100, the requirements of the TSN stream can be met only when the resource management allocates network resources for each hop along the entire path. Consistent with the TSN configuration (802.1Qcc), this is achieved through the interaction between the 5G system 106 and the CNC 112. The interface between the 5G system 106 and the CNC allows the CNC 112 to learn the characteristics of the 5G virtual bridge and allows the 5G system 106 to establish a connection with specific parameters based on the information received from the CNC 112. Bounded latency requires deterministic latency from 5G and QoS alignment between the TSN and 5G domains. For example, if the 5G virtual bridge acts as a TSN bridge, the 5G system 106 simulates time-controlled packet transmission in accordance with the scheduled service (802.1Qbv). For the 5G control plane, the TT in the AF 124 receives the transmission time information of the TSN service class from the CNC 112. In the 5G user plane, the TT at the UE 118 and the TT at the UPF 122 can adjust the time-based packet transmission accordingly. Different TSN service classes can be mapped to different 5G QoS indicators (5QIs) in the AF 124 and PCF 126 as part of the QoS alignment between the TSN and 5G domains, and different 5QIs are handled according to their QoS requirements.
[0040] For time synchronization, the 5G system 106 can implement gPTP of the connected TSN network. The 5G system 106 can act as a virtual gPTP time-aware system and support forwarding gPTP time synchronization information between the terminal station 102 and the bridge 108 through the 5G user plane TT.
[0041] View now Figure 2, which shows a block diagram of a system 200 architecture according to some embodiments of the present technology. Broadly, system 200 can be implemented as an integrated TSN-5G system similar to system 100 described above, and also includes physical components similar to the physical components in system 100 discussed above. However, unlike system 100, system 200 provides a novel architecture for an integrated TSN-5G system, in which the 5G system 106 is configured as a set of discrete 5G components, each of which is configured to simulate a discrete TSN block 202. In other words, in system 200, the 5G system 106 is configured as a decomposed structure including multiple TSN blocks 202-1 to 202-N, each of which is configured according to the TSN specification (e.g., in accordance with IEEE 802.1 and related standards discussed above), such as as a TSN bridge, a TSN terminal device, or a combination of both. In addition, instead of having a centralized configuration controller 110 to control the TSN-5G system, the present technology provides multiple distributed configuration modules 215 in the distributed controller 210 in the TSN-5G system 200. The configuration modules 215-a to 215-f can be interconnected in one or more topologies (mesh, star, tree), and each configuration module 215 can be responsible for communicating with one or more TSN blocks 202 and configuring the blocks. As used herein, "topology" can refer to one or more arrangements of a network, which may include multiple nodes (e.g., sender devices, receiver devices, switches, or bridges) and connecting lines between nodes in the network (e.g., communication links, or "jumps" including wired communication links or wireless communication links). Each link can couple a corresponding pair of nodes in a communication manner. A set of links can be coupled in sequence via their corresponding nodes to define, for example, a link path between a source node and a destination node. The topology may include, but is not limited to, one or more of a mesh, star, bus, ring, and tree topologies.
[0042] In some embodiments, the system 200 is configured to support and manage deterministic TSN data flows between a data source 204 and a data destination 206 via the 5G system 106 according to a TSN configuration including a TSN schedule determined by one or more of the configuration modules 215. The data source 204 and the data destination 206 may include one or more of the I / O device 102 and the controller 104. Although not shown, the system 200 may also include a TSN bridge 108 and other TSN components.
[0043] In some embodiments, in the decomposed structure, each of the plurality of TSN blocks 202-1 to 202-N may correspond to a 5G system, for example, Figure 1 1 and discussed above. For example, Figure 3As shown in , UE 118 may be configured to simulate a TSN block 202-1, RAN 120 may be configured to simulate a TSN block 202-2, UPF 122 may be configured to simulate a TSN block 202-3, and the core network and / or other typical components of the 5G system (e.g., fronthaul, backhaul, multi-access edge computing (MEC) module) may be configured to simulate one or more TSN blocks 202-N. Each TSN block 202-1 to 202-N is configured, for example, as a TSN bridge, a TSN terminal device, or a combination of both according to the TSN specification (e.g., in accordance with IEEE 802.1 and the related standards discussed above).
[0044] In some embodiments, such as Figure 4 As shown in FIG. 4 , each TSN block 202 includes a processor 402, a memory device 404, an internal configuration interface (ICI) 406, a transmission module 408, a reporting module 410, and TSN translators (TT)-1 412-1, TT-2 412-2, and TT-3 412-3. The processor 402 may be a microprocessor or a multi-core processor, an integrated circuit, a field programmable gate array, etc., which processes TSN configuration data and executes instructions (e.g., stored in the memory device 404) to process and transmit TSN data traffic from one or more TSN data streams according to the TSN configuration data.
[0045] The memory device 404 may store parameter sets describing the ability to support and execute data flows (e.g., carrying URLLC data services) through the corresponding TSN block 202. In some embodiments, the parameter set includes, but is not limited to, identity, link quality, and link bandwidth. The identity parameter may include the device type (i.e., whether the TSN block 202 is a TSN bridge or a TSN terminal station). The delay parameter may include at least the port-to-port (from the beginning of the TSN block to the end of the TSN block) delay, and the delay variation (commonly referred to as "jitter"). The link quality parameter may include at least the packet error rate. The link bandwidth parameter may include at least the available bandwidth in bits / second.
[0046] In some embodiments, the parameter set for the TSN block 202 may include a subset of parameters specific to the 5G RAN, including short transmission time intervals, TSC assistance information (TSCAI), configured grant (CG) information, semi-persistent scheduling (SPS) allocations, and / or other parameters specified in, for example, 3GPP TS28.540. In addition, in some embodiments, the parameter set for the TSN block 202 may include a subset of parameters specific to TSN, including time synchronization properties, scheduled transmission (Qbv) properties, redundancy properties including the number of RANs connected to the UPF, the number of paths, path diversity, the number of available frequencies, propagation characteristics, available radios, different physical media (e.g., free space optics). For example, Figure 5 An example parameter set 502 for an example TSN block 202 is shown.
[0047] In some embodiments, a parameter set for the TSN block 202 may define a worst case time synchronization error, a worst case gate operation error, a maximum gated list size, a maximum cycle time, a maximum gate interval duration, a transmission start delay, the like, or a combination thereof. The parameter set may include a discrete set of deterministic parameters that may vary by the type of traffic handled by the TSN block 202. The parameter set may be used, at least in part, to generate a TSN schedule, configuration, or the like that may be implemented on the hardware of the TSN block 202. In the absence of such a parameter set, the TSN scheduling module must take a lowest common denominator approach, where all devices of the system 200 that include the TSN block 202 are assumed to have the most restrictive characteristics that produce a suboptimal solution. In this sense, the parameter set enables a better scheduling solution in the TSN system 200, resulting in improved performance metrics including latency, jitter, packet delay variation, and bandwidth utilization.
[0048] In some embodiments, the parameter set of the TSN block 202 may further describe or relate to devices generated, programmed, or otherwise obtained by different operations or manufacturers. In this sense, the parameter set may define a collection or subset of different devices (e.g., heterogeneous, such as from multiple vendors), rather than homogeneous or similar devices. For example, the parameter set may include, but is not limited to, the definition of a specific configuration model, error tolerances, hardware limitations, software limitations, and firmware options for each end node and switch node in the system 200. In this sense, the parameter set enables scheduling and configuration of heterogeneous networks including devices from multiple vendors and with varying characteristics.
[0049] In some embodiments, the parameter sets of the TSN block 202 may further define specific TSN features supported by each end node and switch node in the TSN system 200. For example, the parameter sets may define whether a node or TSN block 202 supports one or more of time synchronization, time-aware shaping, asynchronous shaping, frame duplication and reliability elimination, frame preemption, ingress policing, and other TSN features. The parameter sets may further define specific versions or variations of features or standards supported by the end nodes and switch nodes in the TSN system 200. These parameter sets enable scheduling and configuration of mixed-capability networks, where the end nodes and switch nodes have varying degrees of support (including no support) for desired TSN features and versions.
[0050] Another non-limiting example of a parameter set for a TSN block 202 device may include, but is not limited to, additional parameters for programming the functionality of the respective TSN block 202. For example, the additional parameter set may define or enable programming of the respective TSN block 202 with the generated or scheduled TSN configuration. Non-limiting examples of parameter sets may define or enable programming of the respective TSN block 202 may include, but are not limited to, programming methods, communication protocols, device login names, device login passwords, device programming ports, device programming file structures or file paths for programming data, device programming file formats, device configuration file formats, device schedule file formats, the like, or combinations thereof. In this sense, such parameter set or subset defines or enables programming of the respective TSN block 202 with the generated or scheduled TSN configuration (collectively, “programming parameters”), and enables or allows the system 200 to update, install, program, configure, or otherwise modify the set of TSN blocks 202 to operate in response to or according to the schedule or configuration of the TSN system 200.
[0051] Furthermore, each TSN block 202 may include at least one internal configuration interface (ICI) 406 configured to support interaction of the TSN block 202, for example, with its corresponding configuration module 215. The ICI 406 may be used to provide some or all of the parameter sets of the TSN block 202 to the corresponding configuration module 215, and to receive configuration data (e.g., transmission schedules, data flow identities, regulatory rules, etc.) from the configuration module 215 to support one or more data flows through the TSN block 202. Each TSN block 202 may be configured to perform or operate according to the configuration data (received via the ICI 406), and to transmit data for each data flow according to the specifications provided in the configuration data.
[0052] In some embodiments, the configuration data received via the ICI 406 at the TSN block 202 from its corresponding configuration module 215 may include stream identification information, transmission schedules or deadlines or delay budgets, or (for rate-limited services) data rates, filtering and policing configuration information, redundancy schemes, and / or other TSN configuration information.
[0053] TSN speaker information can be separated into different frequency components that require different TSN stream latency and determinism requirements. Conversely, TSN streams from different TSN speakers can be aggregated into a single TSN stream to achieve greater capacity and higher channel utilization. Having discrete cycle times in an integrated TSN-5G system can help ensure ease of TSN stream aggregation.
[0054] In some implementations, each TSN block 202 may include a transmission module 408 configured to send transmissions of a particular data stream in accordance with a schedule, deadline, delay budget, or data rate in configuration data received from the configuration module 215 via the ICI 406. In one example where the TSN block 202-1 corresponds to a UE 118 of a 5G system, the transmission module 408 is configured to send data transmissions based on resource scheduling of the 5G air interface (between the UE 118 and the RAN 120). The resource scheduling of the 5G air interface may be aligned in phase with the cycle time of the integrated TSN-5G system. The transmission module 408 may assign resource elements in the 5G component corresponding to (of which 408 is a part) the TSN block 202 in a manner that enables compliance with the scheduled transmission for each Qbv stream. For example, instead of using classic 802.1Qbv-style gate control, the UE 118 corresponding to the TSN block 202-1 may use a phase offset (referenced to the cycle time) to align the transmission of the TSN data stream with the assigned schedule. In this example, instead of UE 118 obtaining this phase offset from the CNC, UE 118 may obtain the phase offset from RAN 120 as a special command.
[0055] In some implementations, each TSN block 202 may also include a reporting module 410 configured to monitor the runtime behavior of the TSN block 202 and report the behavior through the ICI 406 or via a separate interface of the TSN block 202. This behavior monitoring includes metrics including, but not limited to, packet loss conditions and missed transmission windows.
[0056] Return to view Figure 2, the present technology provides multiple distributed configuration modules 215 in the distributed controller 210 in the TSN-5G system 200. The configuration modules 215-a to 215-f can be interconnected in one or more topologies (mesh, star, tree), and each configuration module (CM) 215 can be responsible for communicating with one or more TSN blocks 202 and configuring the blocks. For example, CM 215-a can be responsible for and operationally and communicatively connected to TSN blocks 202-1 and 202-2. CM 215-b can be responsible for and operationally and communicatively connected to TSN block 202-3. CM 215-c can be responsible for and operationally and communicatively connected to TSN blocks 202-3 and 202-N. Thus, TSN block 202-3 can be configured and controlled by CM 215-b and CM 215-c. For example, a portion of the functionality at the TSN block 202-3 (e.g., with respect to a first type of TSN application) may be configured and controlled by the CM 215-b, and another portion of the functionality at the TSN block 202-3 (e.g., with respect to a second type of TSN application) may be configured and controlled by the CM 215-c.
[0057] exist Figure 2 In the example shown in , configuration modules 215 are arranged in a tree structure, where CM 215-f forms the highest level of the tree structure, CMs 215-a, 215-b, and 215-c form the lowest level of the tree structure, and CMs 215-d and 215-e are between the highest and lowest levels of the tree structure. However, configuration modules 215 are operatively and communicatively connected to each other via API 230. In some embodiments, in a tree structure (e.g., such as Figure 2 ), a configuration module 215 can communicate with other configuration modules 215 at an adjacent tree level (one tree level higher or lower). However, in other topologies (e.g., in a mesh or peer-to-peer structure), any two configuration modules 215 in a distributed controller 210 can be directly operatively connected to and communicate with each other.
[0058] In some embodiments, each configuration module 215 may be an external facility responsible for configuring one or more corresponding TSN blocks 202, or may be configured as a software module within the TSN block 202. Each configuration module 215 may be configured to determine configuration data including a TSN schedule for one or more data streams to be transmitted through the TSN block 202 and provide the configuration data to the TSN block 202 controlled by the configuration module 215. The configuration modules 215 may exchange information with each other using a standardized API 230. The exchanged information may include information about the cycle time of the TSN system (e.g., supported administrator cycle times (ACT), discrete levels including ACT buckets each corresponding to a specific data stream, maximum / minimum cycle times), configuration data including a transmission schedule for one or more TSN blocks 202 (including time offset / duration / resources for transmission), and information to request or respond to a request for resource allocation. In some embodiments, one or more of the configuration modules 215 may be configured as the CNC 112 and / or CUC 114 of the TSN controller 110 discussed above.
[0059] In some embodiments, each configuration module (CM) 215 receives some or all of the parameter set (discussed above) for the TSN block 202 from the ICI 406 of the TSN block 202 controlled by the CM 215. The CM 215 also receives information about data flows to be configured by the TSN block 202 from another entity in the system 200 via the API 230. In a non-limiting example, the data source 204 and / or the data destination 206 provide the requirements for the data flows between the data source 204 and the data destination 206 to the CM 215 directly or via an intermediary such as the CUC 114. In some embodiments, the CM itself may allow a user to define a set of data flows to be configured via a user interface. As used herein, information about data flows may include or define a set of data flows, data streams, transmission paths (predetermined or otherwise adapted), or the like, to define a desired TSN communication path between the data source 202 and the data destination 206. A non-limiting example set of information about a data flow may include maximum allowable latency, data rate, data frame size ("payload"), data frame destination, frequency band allocation gap, the like, or a combination thereof.
[0060] Based at least on the received data flow information and the parameter set for the TSN block 202, the CM 215 determines a "solution" (or configuration data), where the solution will indicate how to handle each data flow through the TSN block 202. This solution may include time-aware schedules, policy-making rules, and other matters, as discussed in U.S. Application No. 17 / 100,356, which is incorporated herein by reference in its entirety. The CM 215 may then send this solution or configuration data to the TSN block 202 via the ICI 406. The TSN block 202 may then execute this solution and transmit data for each flow according to its configuration. In some embodiments, as an example process of having the distributed CM 215 compute a solution, at each level of the tree structure of the CM 215, the same system module theory (SMT) solver may be used, where the data flows and their requirements are expressed as constraints, and a linear programming method is used to solve for feasible solutions. The solution from a lower level of the CM tree is input as used resources (again represented by constraints) at a higher level on the CM tree. This process is repeated until the topmost level of the CM tree is reached, where the global solution is determined.
[0061] In some embodiments, different data sources (e.g., data source 204) and their applications operate at different cycle times or intervals. Relatedly, different data sources and destinations (and their applications) require different levels of time certainty for many data flows therebetween. In conventional TSN systems, a converged cycle time (commonly referred to as an "administrator cycle time") is determined that applies to all data flows in the network. However, in some embodiments of the present disclosure, an integrated TSN-5G system may use a discrete / quantized set of cycle times in the network. Each data flow selects one of the available quantized cycle times to operate. The scheduling in the TSN-5G system 100 for scheduled transmission may be based on a quantized / discrete set of cycle times. For example, the integrated TSN-5G system 100 may limit the available stream interval and therefore the corresponding cycle time to a discrete value set, including but not limited to substantially 1, 10, 100, 1000 milliseconds. Similarly, stream or data flow requirements may be limited, for example, jitter (packet delay variation) requirements may be limited to a predetermined discrete value set, including but not limited to substantially 1, 10, 100, 1000 microseconds. In some embodiments, different sets of discrete values may be used, depending on the applications and use cases supported by the integrated TSN-5G system. For example, a geographically dispersed system may use discrete cycle times in milliseconds. In yet another example, a system limited to a local plant may use discrete cycle times in microseconds. Rather than defaulting to a continuous set of cycle times, the members of this discrete set may be regularly or irregularly spaced or follow other statistical distributions (including but not limited to logarithmic, linear, Gaussian). In another embodiment, the set of cycle times is standardized so that all TSN blocks have a cycle time that is the product of elements selected from a small common prime set. This ensures that all composite cycle times will be easily calculated by the TSN scheduler and result in a common network cycle time.
[0062] Each TSN block in the integrated TSN-5G system can support a set of cycle times (wherein the set includes one or more cycle times). CM 215 configures the TSN-5G system 106 or 200 to implement the scheduled transmission of data streams across TSN blocks 202 operating at different cycle times. In some embodiments, TSN blocks 202 may need to operate with compatible cycle times, where compatibility implies that the cycle times are integer harmonics of each other. When the interval requested by the application does not directly map to the available set of discrete cycle times of the TSN block 202 set traversed by the stream, CM 215 can fit to the closest available cycle time. The closest available cycle time will be an integer multiple or integer divisor of the available cycle time. CM 215 can exchange quantized / discrete sets of supported cycle time information with each other during the configuration process. In this example, the present disclosure allows a decomposed TSN-5G system to create a feasible configuration for a large number of data streams / streams. In the absence of quantized cycles / intervals, configuration usually requires a lot of computing time and may even hinder the discovery of feasible solutions.
[0063] In some cases, each integrated TSN-5G network slice in the 5G system 106 may have a predefined supported cycle time and jitter limit set. In some instances, according to the 3GPP specification 23.501 incorporated herein by reference, network slices may be more granular than typical 5G network slices. In some embodiments, the TSN-5G system 106 or 200 may be sliced based on the TSN cycle time. For example, a 5G network supporting multiple critical services may have periodic URLLC slices dedicated to applications and their streams. For example, a service with an application operating in an approximate 1 millisecond cycle may have a dedicated slice operating in a 1 millisecond cycle time. Similarly, services and applications operating in a 100 millisecond cycle (or interval) may have a dedicated slice in an integrated TSN-5G system operating in a 100 millisecond cycle time. Such cycle time slicing improves configuration speed and overall network performance. In some embodiments, the TSN block 202 discloses the cycle time supported for a given slice to its corresponding CM 215 through its ICI 406. The CMs 215 may in turn exchange cycle times for TSN block support with each other under their management via the inter-configuration module API 230 in order to create a configuration solution for a sliced TSN-5G system.
[0064] In some embodiments, the solution or configuration data determined by the CM 215 may include, but is not limited to, a set or group of configurations, timings, commands, controls, instructions, the like, or combinations thereof, for operating the respective TSN blocks 202 according to the characteristics of the TSN blocks 202 (e.g., defined by a set of parameters). In some aspects, the configuration data may include specific transmission information for individual or collective (e.g., "global") data frame transmissions of one or more respective TSN blocks 202. The transmission information may include time information for the transmission of the data frame. In one or more aspects, the configuration data for the data frame may include a transmission start time. For example, the transmission start time may be the time at which the transmission of the data frame from the respective TSN block 202 is initiated. In one aspect, the transmission of the data frame may be initiated by selectively opening the gate of the respective TSN block 202 to transmit the data frame as a data stream to a destination node (e.g., another TSN block 202). Conversely, the transmission of the data frame may be stopped or prevented by selectively closing the gate of the respective TSN block 202 that transmits the data frame. The configuration data may also define or assign a specific path or link that communicatively couples the respective TSN block 202 and another node to transmit the data stream over. Additionally, the configuration data may define a duration of transmission of the respective data stream from the respective TSN block 202. In one aspect, the duration of the data stream transmission may be defined by a time period between selective opening of a gate of the respective node (i.e., to transmit a data frame) and selective closing of the gate (i.e., to stop transmitting the data frame to the target node).
[0065] In conventional TSN systems, the TSN schedule is expressed as an absolute time offset in a periodic cycle in which the TSN block is instructed to transmit the data. However, this may be too restrictive for a 5G system 106 composed of components from multiple vendors. In some embodiments, a deadline-based schedule is determined by CM 215 and provided together with configuration data. A deadline-based schedule may indicate that the TSN block 202 transmits data of a configured data stream no later than a deadline (expressed in terms of absolute time in a periodic cycle). In some embodiments, a delay budget-based approach will indicate that the TSN block transmits data frames of a configured data stream within a delay budget. Therefore, under a delay budget-based approach, the TSN block 202 needs to send data frames that arrive at its inlet port within a certain duration to its outlet port. This scheme will not require each TSN block 202 to be time synchronized. In some embodiments in which the TSN block 202 is configured under a rate constraint, the TSN block 202 is configured to transmit data frames of a given data stream in a manner that does not exceed a configured value (according to the configuration data from CM 215) at an average or peak transmission rate (in bits per second).
[0066] In some 5G systems, a TSN block may be a set of shared resources that are made available by network slicing based on a service profile that defines network latency, with a periodic cycle including but not limited to delay / budget. In such embodiments, there may be two levels of scheduling, where in addition to slice-level TSN scheduling, 5GS TSN-AF may also enable the TSN block 202 to be configured as a shared resource. In either case, configuration attributes such as resource identifiers may identify TSN blocks for appropriate configuration. For example, a service provider may have multiple service profiles with specific periodic cycles, and multiple tenants of the service provider may utilize the same TSN blocks as those specified by the 5GS TSN-AF configuration and may perform TSN stream aggregation. In some embodiments, a service provider may provide a set of non-shared TSN blocks, in which only a single-layer service profile may exist. Device-specific operations / required resource sharing modes may be available to CNC 112 via TSN-AF.
[0067] As an example implementation of the deadline / delay budget method of the TSN block 202, when a data frame arrives at the ingress port of the TSN block 202, the TSN block 202 will mark the arrival time of the data frame using its local clock. The TSN block 202 can then identify the frame as belonging to a configured data stream and can then start a countdown timer equal to the configured delay budget of the data stream. Using the transmission module 408, the TSN block 202 can prioritize the transmission of data with the least amount of time left. If the timer for a packet expires before the packet is transmitted, the event is recorded as a lost transmission and is considered in the monitoring metrics by the recording module 410.
[0068] In some embodiments, the scheduled transmission between TSN block 202-1 (corresponding to UE 118) and TSN block 202-2 (corresponding to RAN 120) may involve "enhanced" allocations (assignments and transmissions) of uplink and downlink transmissions between UE 118 and RAN 120 in order to meet the schedule assigned by CM 215-a for TSN block 202-1 corresponding to UE 118. In some embodiments, CM 215-a may take into account the UE 118 buffer status and radio conditions reported by RAN 120 when instantiating the TSN schedule, and may adjust or report the required changes in the requested schedule. In some other embodiments, CM 215-a may send real-time feedback on radio conditions received from RAN 120 to a master CM, such as CM 215-d. This feedback loop may support recalculation of the TSN schedule at this particular TSN block or across TSN blocks on a given end-to-end path to meet the packet delay budget.
[0069] In this embodiment, link quality can be monitored, and CM 215-a can continuously adjust the radio resources in the configuration data to meet the transmission schedule. Radio resources may include, but are not limited to, logical channels, transmission power, and UE-specific time slot durations. In some embodiments, static assignments of fixed / deterministic uplink and downlink time slots for a given UE 118 may be made, such that, for example, all UEs connected to a given RAN slice are given scheduled transmission time slots. 5G native air scheduling can be used to determine whether a transmission from UE 118 will meet a transmission deadline. If not, UE 118 can request access to RAN 120 for schedule transmission. In some embodiments, scheduling in a 5G system 106 for scheduled transmission may be based on a quantized / discrete set of cycle times, wherein the set includes an administrator cycle time of at least 100 milliseconds. According to the present technology, a radio link between a UE (e.g., represented by TSN block 202-1) and a RAN (e.g., represented by TSN block 202-2) may be split based on cycle time. In some embodiments, the uplink and downlink between TSN block 202-1 and TSN block 202-2 may have radio resources allocated to each network slice based on the cycle time of the slice. For example, a 1 millisecond cycle time slice will require radio resources (channels, flight time, etc.) that can deliver data at a 1 millisecond rate.
[0070] In some embodiments, 5G resource elements (e.g., frequencies and time slots) can be scheduled so that they meet TSN stream latency requirements in addition to "standard" 5G scheduling service prioritization requirements. More specifically, 5G time slots for TSN streams can be allocated so that they transmit messages for TSN streams with appropriate cyclic time offsets (phases) and within the time limits (TSN window times) required by the TSN schedule. In this case, the 5G scheduler differs from a "traditional" TSN Ethernet port in that multiple messages can be sent simultaneously if transmitted at different frequencies. In some aspects, in the presence of poor RF channel conditions, the 5G system 106 can send multiple copies of messages over different frequencies to increase the probability of meeting transmission schedules and / or deadlines.
[0071] In order to achieve reliable data transmission in the system 200, redundant flow paths can be implemented. The decomposed TSN block 202 of the 5G system 106 allows errors (delayed, dropped or damaged frames) to be handled in a better manner. In some embodiments, the UE 118 can initiate two redundant non-overlapping PDU sessions to the UPF 122 for redundancy, in which case the 5GC can configure the NG-RAN for dual connectivity according to 3GPP38.300. In some other embodiments, FRER may be used between some TSN blocks 202 and not between other blocks. For example, redundant streams can be implemented through the air interface between the UE 118 (TSN block 202-1) and the RAN 120 (TSN block 202-2) and then combined at the RAN 120, and can be split again through the core network (TSN blocks 202-3, 202-4) when needed. As Figure 1 As shown, the current redundancy requirement according to 3GPP 23.501 is the maximum disjoint paths between UE 118 and UPF 122. However, according to the present technology, redundant disjoint paths do not need to be established across the entire 5G system, but can be implemented only for a portion of the 5G system. For example, in the case of an air interface between UE 118 and RAN 120, the redundancy requirement may specify that the two paths should be on different frequencies or different MIMO channels or different time slots. In some instances, the present disclosure allows flexible use of redundancy, including but not limited to more than two data paths, merging and splitting of data streams between TSN blocks, and support for TSN blocks with different degrees of redundancy capabilities.
[0072] The concept of segmenting 5GS into multiple TSN blocks (e.g., as described above with respect to Figure 2) can potentially enhance security in situations where strict scheduling can hinder the flow of malicious traffic between the blocks. However, enabling 5GS to operate as multiple TSN blocks can introduce security vulnerabilities primarily through configuration. Specifically, TSN users can become aware of internal 5GS details and connectivity that affect other users sharing the same physical and logical infrastructure. This can occur during the required TSN network discovery phase (e.g., information returned via the Link Layer Discovery Protocol (LLDP)). TSN users may also misconfigure their own or other users' configurations. This can be partially addressed using the concept of NETCONF for secure subtrees, where users have limited vision of their own data model subtrees. 5G systems may inherently have the concept of isolated network slices, depending on, for example, whether TSN is implemented virtually (via software) or physically (via hardware). Infrastructure providers may have to set restrictions on what physical and logical capabilities are exposed to each TSN user. This can be accomplished via 5G Network Open Functions (NEFs). The present disclosure provides a solution to security issues by using "virtual TSN blocks". Virtual TSN blocks are internal 5G TSN blocks that only contain capabilities provided by the user's 5G network slice. In other words, the user can only see and configure the TSN block information exposed via the 5G network slice, and no more than that TSN block information. In this sense, the internal 5G TSN block is the intersection of the set of information contained in the internal TSN block and the 5G network slice provided to the user.
[0073] In some embodiments, the IETF DETNET standard (as provided at the IETF: "Deterministic Networking Working Group" - https: / / datatracker.ietf.org / wg / detnet / about / ) may be implemented or integrated into the 5GS to interconnect islands of smaller Ethernet networks that conform to TSN. The 5GS may utilize DETNET to enable the transmission of TSN messages over IP layer 3 (rather than layer 2). Envisioning such a system, the techniques discussed in this disclosure include a 5GS that supports DETNET edge, relay, and interconnecting transport nodes of spatially separated TSN networks to create a larger composite TSN over 5G. All aspects of the integrated TSN-5G system provided in this disclosure are applicable to (but not limited to) the TSN islands of the 5G DETNET, and in particular the TSN blocks of the decomposed TSN.
[0074] DETNET includes the following components: (1) TSN terminal system: IEEE consistent terminal system that communicates with DETNET edge nodes (2) DETNET edge nodes: process TSN frames into DETNET (3) DETNET relay nodes: (4) DETNET transit nodes: provide congestion avoidance for time-sensitive messages. DETNET is routed rather than bridged, thus enabling routable TSN messages between TSN LANs. Basic TSN Ethernet frame information is transmitted between LANs or reconstructed during transmission. DETNET implements its higher-level functions by adding sublayers: (1) DetNet service sublayer: provides DetNet services (e.g., service protection) to higher layers in the protocol stack and applications, and (2) DetNet transport sublayer: supports DetNet services for DetNet flows in the underlying network (e.g., by providing explicit routing and congestion protection) and encapsulates TSN Ethernet frames. DETNET routing incorporates IP header modifications according to standard router behavior, such as time-to-live (TTL processing), where the TTL specifies the maximum time a routable IP message is allowed to live, explicitly related to the TSN maximum latency requirement.
[0075] The DETNET component may reside in any computing element of the 5GS, especially in the 5G MEC or core. Therefore, in one embodiment, the 5GS may be a fully compatible DETNET interconnecting the TSN LAN. In order to provide determinism, DETNET may reserve data plane resources for the DetNet stream in some or all intermediate nodes along the path of the stream. DETNET may provide explicit routing for DetNet streams. DETNET may allocate data from DetNet stream packets in time and / or space to ensure the delivery of data for each packet, regardless of the loss of the path. Therefore, as described above, the TSNNCNC / DNC and scheduler may need to interact with DETNET, especially the ability to configure the stream path (including redundant stream paths), TTL and obtain routing delay and jitter. TSN service shapers, time-aware shaping and network calculus can be used to achieve the desired level of determinism in 5GDETNET.
[0076] It should also be noted that a hybrid 5GS where part is TSN (layer 2) and part is DETNET (layer 3) can coexist and interoperate. In such a case, the DETNET portion of the network itself can be processed as (one or more) TSN blocks 202, as discussed above.
[0077] Additionally, with respect to caching within the 5GS to minimize latency and increase determinism for TSN applications, the storage, location, and naming of information in the 5GS can be managed in a manner that enables fast and shorter proximity access to minimize jitter. Each piece of information can be cryptographically signed to increase the security and access provided by the cryptographic signature and hashing of the information stored in the 5GS components, such as the MEC. The cache forwarding unit will track each data request to allow for optimal forwarding, placement, and servicing of cached data. The TSN CNC / DNC and scheduler can calculate where to locate the cached information within the network (particularly the 5GS) to maximize access and minimize jitter (packet delay variation) between 5G applications.
[0078] Real-time MEC applications typically have a well-defined characterization of their behavior. Cloud (cloud computing) and fog (fog computing) 5G MEC applications can be split into microservices with hard real-time constraints provided to the TSN scheduler. The constraints can be a well-defined statistical description of the longest (worst case) time to complete a call to a service or a network calculus requirement according to an arrival or service curve. In some embodiments, microservices can be linked together to create a complete MEC application. By dividing the computation into a series of smaller microservices, each service can be better controlled and managed and more determinism can be provided. Each microservice can be abstracted as an internal TSN block, including deterministic inputs, outputs, schedulable operations, and coordination with the 5G-TSN AF. Microservices can reside on the same or spatially different processing systems interconnected by TSN scheduled communications.
[0079] This hard real-time processing may include 5G MEC and 5G core functions. Messages in and out of the MEC TSN block follow a deterministic schedule that can be calculated by the TSN scheduler. It should be noted that such TSN blocks will be referred to as "compute TSN blocks". Considering that the messages generated by the MEC and their corresponding sizes and transmission times may vary depending on the computational complexity of the MEC processing tasks, the processing load, and the application state, the TSN scheduling component may utilize an internal model that is a simulation, emulation, or pure analysis or hybrid (also known as a digital twin) of each of the MEC processors for TSN scheduling purposes. The TSN scheduling component may then generate a complete end-to-end TSN schedule for all messages flowing between the 5GUE, MEC, and 5G core, as well as any cloud processing required for real-time applications, where the 5G core and cloud processing are similarly modeled by the TSN scheduler. The TSN schedule can dynamically recalculate the schedule as needed to maintain the required determinism for 5G TSN real-time MEC / cloud applications because the effective processing rate and therefore the output message transmission time will change. The TSN scheduler can provide feedback to application developers (and for management and deployment) about the best location (UE, MEC, cloud) for each processing component of a real-time 5G application, taking into account link speed, variation, processing power, available memory, etc. The TSN system can adopt a gate-based approach or a rate control mechanism, such as a leaky bucket, and can use any number of optimization techniques or network calculus to determine a feasible schedule. Therefore, the complete flow of a TSN application will not only contain the end-to-end path through the network for a particular message, but also the complete processing path through all computing TSN blocks (microservices) that act on the information in the message. IEEE 802.1CB redundant paths can be configured by redundant or parallel computing TSN blocks (microservices). In the present invention, it should be possible to observe the complete real-time processing activities encoded in the TSN schedule, where the computing TSN blocks appear as Ethernet bridges, except that they either process messages or can create new messages that are transmitted on a deterministic schedule.
[0080] MEC applications are configured to use TSN flows (to participate as TSN speakers or listeners) using NETCONF, RESTCONF, or RESTful APIs. The messages defined in the aforementioned protocols contain the IEEE 802.1Qcc information required to configure the TSN flows used by the MEC applications. In addition, MEC applications are designed to move from one MEC platform to another, and the RESTful API is defined to query the TSN configuration of the current platform to verify that it has the required deterministic communication requirements, specifically, including latency and jitter. It also has an updated RESTful API containing the aforementioned information required to notify the TSN CNC of its new location and the information required to dynamically reallocate TSN traffic to its new location. As mentioned, IEEE 802.1CB can be used to establish redundant TSN flows to the intended location where the MEC application can migrate. The TSN scheduler, i.e., a centralized network configurator (CNC) or a distributed network configurator (DNC), can be a MEC application that provides 5G TSN scheduling as a service and configuration as a service, which can be used for dynamic rescheduling, where low latency is required.
[0081] TSN applications can transmit timing performance profile query microservice requests, with the goal of determining statistical information about processing time. When responding to such requests, the microservice will execute the request and return both the result and the timing performance profile. The timing performance profile may contain at least the network start and end time of the microservice call, and may optionally contain the start and end time of all called sub-functions. The information may also contain the average value of the MEC processor load during the timing performance profile. The timing performance profile can be used by TSN applications to optimize TSN scheduling, where microservices are required to process TSN traffic flows. The timing performance profile can be obtained during effective operation, where the output from the profile is usually used, or as a special test sample before effective operation. The timing performance profile information can be used to determine which MEC hardware is used for current and future operations and as constraint information for the TSN scheduler.
[0082] The present disclosure also provides additional new aspects, including: (1) TSN scheduling of 5G core functions; (2) ensuring that the CPU has direct time synchronization with the Ethernet hardware timestamp mechanism; (3) enabling TSN scheduling of specific 5G network functions and processes; (4) adding new time-aware programming features, such as time-based event processing; (5) integrating conditional processing based on time, such as real-time programming implemented via YANG configuration of microservice scheduling to implement service chaining (see, for example, https: / / www.rfc-editor.org / rfc / pdfrfc / rfc7758.txt.pdf for YANG scheduled operations).
[0083] In addition, the LinkDelayStatistic (implemented as a YANG model) cumulative distribution function data model may be implemented within the TSN-5G system 106 or 200. In such an implementation, the wireless link may collect information and feed it to the scheduler of the CNC, which will then utilize the information to schedule variable speed links. The LinkDelayStatistic YANG model may also provide information on whether the link delay is static and ergodic. The scheduler may use this information to predict the future and create an accurate schedule depending on a given sample. The CNC may then utilize this knowledge for each TSN block to deploy the best potential TSN traffic shaping or gating schedule, including using network calculus in determining the result.
[0084] The present disclosure also contemplates virtualized network functions (VNF-TSN) that can reside as software within a 5G system. It may require dedicated processor hardware to support real-time operation. In some embodiments, TSN may be provided as software-defined TSN (SDN-TSN) and 5G TSN as a service (TaaS). In some embodiments, VNF-TSN may be configured within each 5G subcomponent (TSN block): UE, Radiohead, CU / DU, RAN, MEC, core, etc. As discussed above, microservices may be linked together as part of TSN scheduling. Each microservice may expose its service time characterization to the TSN schedule. Services are part of the delay, but they may have more variation than communication links. In such embodiments, services are links in this integration of microservices and TSN scheduling. Network computing can be used to incorporate processing delays. TSN inputs provide clear arrival curves. Processor execution time provides service curves (we assume that 5G devices have well-characterized processing times).
[0085] In another aspect of the present disclosure, a time-aware MEC platform is defined as a platform that acts as a PTP client (compliant with 802.1AS terminal stations) and, if necessary, as a PTP bridge (compliant with 802.1AS bridges). PTP bridges and network bridge functionality are required for virtualized MEC platforms that run multiple slices (OSes, VMs, containers) in parallel. Typically, virtual bridges / switches are used in virtualized computing platforms. In the present disclosure, TSN-enabled virtual switches are defined that include time awareness. The time-aware PTP client in the MEC platform runs a PTP state machine and a servo mechanism to synchronize the local available clock with the highest-level clock in the network. In addition, the MEC platform synchronizes the system clock with the PTP clock, where the system includes an operating system, a network stack, an application stack, or any other software and hardware elements that utilize a clock. This enables each MEC application to operate on synchronized PTP time. In one example, the MEC host operates this PTP client and provides synchronized time (such as system / host time) for all MEC applications via a virtualized infrastructure. In another case, each MEC application may run a separate instance of a PTP client connected to the host via a time-aware bridge.
[0086] As a configuration interface, 3GPP 23.501 specifies a centralized configuration model in which the CNC configures the 5GS as a time-aware bridge. Similarly, the MEC platform should be configurable with the CNC as a time-aware end station or a time-aware bridge. This MEC can support configuration using the 802.1Qcw yang model for TSN features, which include time-aware shaping, forwarding, and frame replication and redundancy elimination. In addition, the MEC host may have a CUC component that uses the 802.1Qcc interface to provide the CNC with data flow requirements for resident applications. The MEC can also provide the CNC with information about its TSN capabilities so that the CNC can accurately model the MEC. For example, the MEC itself can appear as a TSN end station that initiates a certain set of data flows. The CNC will appropriately model the MEC in the network and generate the correct configuration. The MEC will support identification of data streams in collaboration with the OS and applications. The specific functionality varies depending on the TSN awareness of the MEC components. TSN-unaware applications on MEC hosts require IP stream identification in the MEC bridge.
[0087] The TSN fronthaul / backhaul (e.g., TSN block 202) may be directly connected to the MEC, thereby providing deterministic input to the MEC. However, MEC applications are intended to continuously migrate, or perhaps more intuitively, "float" to the edge of the 5G network to remain closest to their potentially mobile clients. Therefore, MEC applications that require determinism will specify a minimum acceptable packet delay variation (MPDV) threshold. MPDV may be incorporated into the specifications of all MEC applications, which may limit viable application locations to those MEC platforms that exist as TSN blocks within the 5GS. The application must ensure that the appropriate TSN stream identification and translation rules are implemented on the new MEC platform (which may be a single processor or a sub-network of processors) so that the MEC message speaker / listener message frames are properly labeled and handled. When possible, the MEC application may want to carry its own configuration instructions so that it is "automatically installed" when it migrates to the new MEC platform. It should be noted that a load balancing mechanism may be employed to ensure that users do not over-install any set of MEC applications and that MEC applications are distributed in an optimal manner. In other cases, redundant MEC platforms and applications may be instantiated and / or MEC applications migrated due to noise rather than strictly due to mobility. Multiple MECs may also be connected as a TSN redundant system.
[0088] Fig. 6A and 6B An integrated TSN-5G system 600 (similar to system 200) is shown including a TSN block 605 (similar to TSN block 202-N) representing or corresponding to a multi-access edge computing (MEC) module. TSN block 605 is configured as a data source / sink (i.e., as a TSN end station), but is located within 5G system 106 rather than being arranged at the edge of 5G system 106. TSN block 605 can be configured as a bridging end station.
[0089] See also Figure 8 , the application data stream can span multiple integrated TSN-5G systems 805 and 810. In this case, the TSN blocks can be geographically distributed and interconnected with more than one 5G system using TSN compatible transmission 820 including but not limited to 5G backbone, dedicated network tunnel or other wide area network. In the present invention, the TSN blocks are configured by their corresponding CM 215. In some embodiments, the configuration across the two TSN-5G systems 805, 810 can be coordinated by a centralized configuration facility (CNC) 112. In some other embodiments, the CM 215 between the two TSN-5G systems 805, 810 can communicate directly. In some embodiments, multiple CUCs and CNCs can be used to capture user requirements and generate TSN solutions and technologies (e.g., TSN schedules, forwarding instructions, etc.) provided in this disclosure.
[0090] Figure 7 An electronic system 700 is shown that can be used to implement one or more embodiments of the present technology. The electronic system 700 can be the TSN block 202 and / or the configuration module 215 and / or can be a part thereof. The electronic system 700 can include various types of computer-readable media and interfaces for various other types of computer-readable media. The electronic system 700 includes a bus 708, one or more processing units 712, a system memory 704 (and / or buffers), a ROM 710, a permanent storage device 702, an input device interface 714, an output device interface 706, and one or more network interfaces 716, or subsets and variations thereof.
[0091] The bus 708 collectively represents all system, peripheral, and chipset buses that communicatively connect a number of internal devices of the electronic system 700. In one or more embodiments, the bus 708 communicatively connects one or more processing units 712 with the ROM 710, the system memory 704, and the permanent storage device 702. The one or more processing units 712 retrieve instructions to be executed and data to be processed from these various memory units in order to perform the processes of the present disclosure. In different embodiments, the one or more processing units 712 can be a single processor or a multi-core processor.
[0092] ROM 710 stores static data and instructions needed by one or more processing units 712 and other modules of electronic system 700. On the other hand, permanent storage 702 can be a read and write memory device. Permanent storage 702 can be a non-volatile memory that stores instructions and data even when electronic system 700 is turned off. In one or more embodiments, a mass storage device (e.g., a magnetic or optical disk and its corresponding disk drive) can be used as permanent storage 702.
[0093] In one or more embodiments, a removable storage device (e.g., a floppy disk, a flash drive, and its corresponding disk drive) may be used as the permanent storage device 702. Similar to the permanent storage device 702, the system memory 704 may be a read and write memory device. However, unlike the permanent storage device 702, the system memory 704 may be a volatile read and write memory, such as a random access memory. The system memory 704 may store any instructions and data that one or more processing units 712 may need at run time. In one or more embodiments, the processes of the present disclosure are stored in the system memory 704, the permanent storage device 702, and / or the ROM 710 (each implemented as a non-transitory computer-readable medium). The one or more processing units 712 retrieve instructions to be executed and data to be processed from these various memory units in order to perform the processes of one or more embodiments.
[0094] The bus 708 is also connected to input and output device interfaces 714 and 706. The input device interface 714 enables a user to transmit information to the electronic system 700 and select commands to the electronic system. The input device that can be used with the input device interface 714 can include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). For example, the output device interface 706 can enable an image generated by the electronic system 700 to be displayed. The output device that can be used with the output device interface 706 can include, for example, a printer and a display device, such as a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flexible display, a flat panel display, a solid-state display, a projector, or any other device for outputting information. One or more embodiments may include a device that acts as both an input and an output device, such as a touch screen. In these embodiments, the feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and the input from the user can be received in any form, including sound waves, voice, or tactile input.
[0095] Finally, if Figure 7 As shown, bus 708 also couples electronic system 700 to one or more networks and / or one or more network nodes via one or more network interfaces 716. In this manner, electronic system 700 may be part of a computer network, such as a LAN, a wide area network ("WAN"), or an intranet, or a network of networks, such as the Internet. Any or all of the components of electronic system 700 may be used in conjunction with the present disclosure.
[0096] These functions described above can be implemented in computer software, firmware or hardware. The technology can be implemented using one or more computer program products. Programmable processors and computers can be included in mobile devices or packaged as mobile devices. Processes and logic flows can be performed by one or more programmable processors and by one or more programmable logic circuit systems. General and special computing devices and storage devices can be interconnected through communication networks. The functions disclosed herein can be implemented using quantum computing, pulse coupled oscillation (PCO) / Ising computing.
[0097] Some embodiments include electronic components, such as microprocessors, storage devices, and memories, that store computer program instructions in a machine-readable or computer-readable medium (also referred to as a computer-readable storage medium, a machine-readable medium, or a machine-readable storage medium). Some examples of such computer-readable media include RAM, ROM, compact disk-read only (CD-ROM), compact disk-recordable (CD-R), compact disk-rewritable (CD-RW), digital versatile disk-read only (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable / rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD card, mini SD card, micro SD card, etc.), magnetic and / or solid-state hard drives, read-only and recordable A computer readable medium may store a computer program that is executable by at least one processing unit and includes a set of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as produced by a compiler, and files containing high-level code that is executed by a computer, electronic component, or microprocessor using an interpreter.
[0098] Although the above discussion refers primarily to microprocessors or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions stored on the circuits themselves.
[0099] As used in the specification of this application and in any claims, the terms "computer", "server", "processor" and "memory" all refer to electronic or other technical devices. These terms do not include people or groups of people. For the purposes of this specification, the terms display or displaying mean displaying on an electronic device. As used in the specification of this application and in any claims, the terms "computer-readable medium" and "computer-readable medium" are entirely limited to tangible physical objects that store information in a computer-readable form. These terms do not include any wireless signals, wired download signals, and any other transient signals.
[0100] To provide interaction with a user, embodiments of the subject matter described in this specification may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and pointing device (e.g., a mouse or trackball) by which the user can provide input to the computer. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and the input from the user may be received in any form, including sound, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.
[0101] Aspects of the subject matter described in this specification may be implemented in a computing system that includes a back-end component (e.g., such as a data server), or includes a middleware component (e.g., an application server), or includes a front-end component (e.g., a client computer with a graphical user interface or a web browser), or includes any combination of one or more such back-end, middleware, or front-end components, through which a user can interact with the implementation scheme of the subject matter described in this specification. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), inter-networks (e.g., the Internet), and peer-to-peer networks (e.g., special-purpose peer-to-peer networks).
[0102] Those skilled in the art will appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or a combination of the two. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been generally described above with respect to their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The described functionality may be implemented in different ways for each specific application. Each component and block may be arranged in different ways (e.g., arranged in different orders, or partitioned in different ways) without departing from the scope of the present invention.
[0103] It should be understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of example methods. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process can be rearranged. Some steps can be performed simultaneously. The accompanying method claims present elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented.
[0104] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. The previous description provides various examples of the technology of the present invention, and the technology of the present invention is not limited to these examples. Various modifications to these aspects will be easily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but will be given a complete scope consistent with the language claims, wherein the reference to an element in the singular form is not intended to mean "there is and only one" (unless explicitly stated), but means "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. Pronouns about men (e.g., his) include women and neutrals (e.g., her and its), and vice versa. Titles and subtitles (if any) are used only for convenience and do not limit the disclosure described herein.
[0105] The predictive terms "configured to," "operable to," and "programmed to" do not imply any specific tangible or intangible modification of the subject matter, but are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or component may also mean that the processor is programmed to monitor and control the operation, or that the processor is operable to monitor and control the operation. Likewise, a processor configured to execute code may be understood as a processor programmed to execute code or operable to execute code.
[0106] As used herein, the term automatically can include execution by a computer or machine without user intervention; for example, by instructions in response to a predicate action of a computer or machine or other initiating mechanism. The word "example" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as an "example" should not necessarily be construed as preferred or advantageous over other aspects or designs.
[0107] Phrases such as "aspects" do not imply that this aspect is essential to the technology of the present invention or that this aspect applies to all configurations of the technology of the present invention. The disclosure related to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. Phrases such as aspects may refer to one or more aspects, and vice versa. Phrases such as "embodiments" do not imply that this embodiment is essential to the technology of the present invention or that this embodiment applies to all configurations of the technology of the present invention. The disclosure related to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. Phrases such as "embodiments" may refer to one or more embodiments, and vice versa. Phrases such as "configurations" do not imply that this configuration is essential to the technology of the present invention or that this configuration applies to all configurations of the technology of the present invention. The disclosure related to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. Phrases such as "configurations" may refer to one or more configurations, and vice versa.
[0108] All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether the disclosure is explicitly stated in the claims. The claimed elements should not be interpreted under the provisions of 35 U.S.C. §112(f) unless the elements are explicitly described using the phrase "means for..." or, in the case of a method claim, the elements are described using the phrase "step for..."
[0109] Edge Control
[0110] Messages in control networks must be reliable and exhibit low and deterministic latency. That is, they must be transmitted over the network with minimal latency variation or jitter. Control messages are typically relatively short in length but are critical. Examples include vehicle control (automotive or aviation), power grid monitoring and control (DNP3 and IEC 61850), and avionics full-duplex interactive Ethernet (AFDX).
[0111] Fig. 95G system 900 is shown (similar to 200 and 600 above) including a TSN block representing or corresponding to a MEC module (also referred to as a MEC host). The MEC host includes one or more multi-access edge services, such as a radio network information service (RNIS) and MEC business rules (e.g., including one or more TSN configurations). The MEC host further includes one or more MEC applications. In one example, the MEC application may be a vehicle engine control application that is configured to send engine control data to an aircraft or a car and receive engine control data from an aircraft or a car within a service area of a radio access network (e.g., one or more of a plurality of distributed units of a radio access network). In another example, the MEC application is a power grid monitoring and control application that is configured to send control data to a power grid infrastructure and receive control data from a power grid infrastructure within a service area of a radio access network (e.g., one or more of a plurality of distributed units of a radio access network).
[0112] Wireless systems inherently experience lower reliability, greater latency, and greater message delay variation than wired networks (e.g., wired Ethernet) required for control systems. Wireless 5G messages (e.g., control data) in system 900 are transmitted from user equipment (UE) to the MEC module and back to the UE via the RAN and other centralized telecommunication processing (e.g., user plane function (UPF) and local data network (LDN) processing). Although it is said to be fast and efficient for telecommunication resources, this is a long trip for each wireless 5G message and may result in latency variation and greater chance of message loss. To address this issue, the 3GPP standard adopts the multi-access edge computing (MEC) standard from ETSI to enable the placement of custom processing inside the 5G network.
[0113] In some embodiments, one or more components of the 5G system 900 (e.g., edge-enabled devices, applications, and / or services) may be implemented in accordance with one or more of the following specifications, which are incorporated herein by reference in their entirety: 3GPP TR 23.758 - Study on application architecture for implementing edge applications; 3GPP TS 23.558 - Architecture for implementing edge applications; 3GPP TR 23.748 - Study on enhancing support for edge computing in 5GC; 3GPP TR 33.839 - Study on security aspects of supporting edge computing in 5GC; 3GPP TR 26.803 - Study on streaming architecture extensions for edge processing; 3GPP TR 28.814 - Study on enhancements to edge computing management.
[0114] Fig.10An improved scheme 1000 for implementing MEC in a 5G network according to some embodiments is shown. The radio access network (gNB) includes at least one central unit (CU) coupled to a central network via a backhaul network, and multiple distributed units (DUs) coupled to the CU via a fronthaul network. The CU provides support for higher layers of the protocol stack, such as SDAP, PDCP, and RRC, while each DU provides support for lower layers of the protocol stack, such as RLC, MAC, and physical layers. In some embodiments, there is a single CU for each gNB, but one CU can control and connect (communicatively couple to) multiple DUs (e.g., greater than 100 DUs). Each DU can support one or more cells, so one gNB can control hundreds of cells.
[0115] For 5G networks, CU is a logical node that contains gNB functions such as transmission of user data, mobility control, radio access network sharing, positioning, session management, etc., except for those functions specifically assigned to DU. CU controls the operation of DU on the fronthaul (Fs) interface. CU can also be called baseband unit (BBU), radio equipment control (REC), rural interconnected community (RCC), centralized radio access network (C-RAN) or virtualized radio access network (V-RAN).
[0116] Depending on the functional split option, each DU contains a subset of gNB functionality. Its operation is controlled by the CU. A DU may also be referred to as, coupled to, co-located with, or otherwise associated with a remote radio head (RRH), a remote radio unit (RRU), a resource element (RE), or a radio unit (RU).
[0117] like Fig.10 As shown in, the implementation of MEC in 5G networks can be improved by moving MEC services and / or functions to the DU. Such a configuration reduces latency, makes latency more deterministic, and makes latency more customizable. This improved implementation enables wireless time-sensitive network (WTSN) control applications to reside within the 5G network. A single 5G control application operating in the MEC can control many devices on the wireless network, making it easier to manage and maintain the control software. Through the implementation described herein, MEC can be so efficient and reliable that engine control can be wireless and completely placed within the MEC.
[0118] The aforementioned improvements can be achieved by: (1) accessing 5G MEC services with deterministic network control based on Time Telecommunications Networking (TSN), and / or (2) locating MEC closer to the US using direct connections to 5G fronthaul to achieve even more efficient performance.
[0119] Regarding deterministic access to 5G MEC, this implementation differs from the standard for TSN over 5G (as currently defined in 3GPP) because the MEC application resides within the 5G network and is not directly connected to the UE. TSN has been specified to operate over 5G, assuming that a TSN translator is associated with the UE. Therefore, according to the implementation described herein, the configuration and control of TSN is redesigned for interoperation with MEC.
[0120] Regarding the positioning of MEC, the closer the MEC processing can be effectively positioned near the UE, the better its communication performance can become. There are several ways to bring the MEC processing closer to the user.
[0121] In some embodiments, MEC processing can be closer to the UE by connecting the MEC directly to the fronthaul, especially the fronthaul over TSN.
[0122] In some embodiments, MEC processing can be brought closer to the UE by directly performing MEC homomorphic processing on I / Q data received from (or for transmission via) the corresponding radio unit of the DU.
[0123] In some embodiments, MEC processing can be brought closer to the UE by enabling MEC service migration, through which MEC services can be efficiently migrated between nodes (between DUs) so that the MEC services remain integrated with the fronthaul network and as close as possible to the target application (e.g., a fast-moving aircraft).
[0124] Fig.11 A communication system 1100 is shown that implements an improved scheme (1000) for implementing MEC in a 5G network according to some embodiments. Fig.11 The communication system in is exemplary and may include more or less than one CU, more or less than five DUs, etc. In some embodiments, Fig.11 Edge-enabled devices in an IoT can be interconnected using an edge computer network (ECN).
[0125] like Fig.11The example communication system depicted in the embodiment includes a core network and a radio access network, the radio access network including a CU, the CU (i) being communicatively coupled to the core network via a backhaul network, and (ii) being communicatively coupled to a plurality of DUs via a fronthaul network. Each of the plurality of DUs is co-located and communicatively coupled with a corresponding radio frequency unit (depicted as an antenna), and includes a MEC module. The MEC module of each of the plurality of distributed units includes one or more processors and a memory storing one or more programs to be executed by the one or more processors, the one or more programs including instructions for controlling a time sensitive network (TSN) configuration and executing one or more MEC applications according to the TSN configuration. In some embodiments, the MEC module uses a representational state transfer application programming interface (RESTful API) to configure TSN on the MEC.
[0126] In some embodiments, the MEC module of each of the plurality of DUs is directly connected to the fronthaul network.In some embodiments, the instructions for executing one or more MEC applications include instructions for transmitting and receiving data (e.g., control data) via the fronthaul network according to the TSN configuration.
[0127] In some embodiments, instructions for executing one or more MEC applications (at each of the DUs) include instructions for processing analog user data associated with a co-located radio frequency unit (a radio frequency unit co-located with a particular DU). In some embodiments, the user data is encoded in an in-phase and quadrature (I / Q) signal; and the instructions for processing the analog user data include instructions for processing the I / Q signals according to one or more homomorphic processing functions. Homomorphic processing includes applying a nonlinear mapping to a different domain to which a linear filtering technique is applied, followed by mapping back to the original domain. In other words, homomorphic processing may include converting data received from a CU for transmission via a radio head or from a radio head for transmission to a CU into a linear system (to separate the I and Q signals), processing the converted signal (e.g., analyzing the converted signal according to a particular MEC application), converting the signal back to its original form, and transmitting any signal it receives in I / Q form (to the radio head or CU, whichever may be the case).
[0128] In some embodiments, instructions for executing one or more MEC applications include instructions for performing MEC services on a first DU 1102 among multiple DUs, determining that a user device (e.g., an aircraft UE) associated with the MEC service is moving from a service area of the first DU 1102 to a service area of a second DU 1104 among the multiple DUs, and migrating the MEC service to the second DU 1104 based on the determination (e.g., performing a switching operation between DUs 1102 and 1104).
[0129] In some embodiments, the instructions for migrating the MEC service to the second DU 1104 include instructions for maintaining the integration of the MEC service with the fronthaul network while migrating the MEC service to the second DU 1104. In some embodiments, the instructions for migrating the MEC service to the second DU 1104 include instructions for converting the MEC application to a TSN stream, and migrating the TSN stream from the MEC module of the first DU 1102 to the MEC module of the second DU 1104. In some embodiments, the instructions for migrating the MEC service to the second DU 1104 include instructions for migrating the MEC service via the fronthaul network according to a deterministic stream (e.g., a TSN stream).
[0130] The improved MEC scheme 1000 (as described with reference to the exemplary system 1100) enables a 5G wireless engine control system (e.g., a distributed full authority digital engine control (FADEC)) to be placed within the MEC and communicate with multiple aircraft in real time and simultaneously via 5G. The 5GS engine control software is fast, deterministic, and reliable using direct integration of MEC with the forward transmission and low-level I / Q data processing achieved through this improved scheme. MEC exposes low-level I / Q data to MEC application developers, enabling efficient programming, similar to combinatorial code processing on a computer, including the ability to inspect raw I / Q data without the overhead of converting to bits (if necessary). Finally, when a MEC application migrates from one MEC platform to another, the MEC application itself is converted into a TSN stream, and its migration should be completed in a fast, deterministic time, especially in unexpected emergency situations that are not pre-positioned.
[0131] Resource representation of 5G MEC container applications
[0132] As discussed above, 5G MEC is intended to improve real-time performance on 5G networks. However, conventional networks do not have a standard way to characterize MEC performance (e.g., processing time, system latency, processing determinism, available load, UE speed, etc.). This disclosure describes some examples of standard ways to characterize MEC performance for requested QoS.
[0133] In some embodiments, the performance characterization metric may represent, for example, processing time, system latency, available capacity, available load, UE speed, and / or processing certainty as a function of the load of the MEC processing system (e.g., the MEC system in the above-mentioned system 600 and / or the MEC host in the system 900). The MEC processing system may use the performance characterization metric as a basis for deciding whether and how to manage TSN service flows and / or MEC application processing rates among DUs in the network. In other words, the MEC processing system may select which DU (which MEC) the application will migrate to based on the performance characterization metric of each MEC in a plurality of candidate MECs within the range of the UE. Thus, the performance characterization metric provides a way to determine and compare the capabilities of multiple MECs for accepting TSN services corresponding to one or more MEC applications (i.e., for MEC planning, switching, and migration).
[0134] The characterization of MEC performance can be used as a basis for determining which DU should be selected for handover of MEC applications.
[0135] Performance characterization metrics may be associated with data tags for data processed by the MEC processing system. Example data tags include metadata describing aspects of the underlying data, elements of the YANG model, and / or the RESTful API. In some embodiments, a multi-tag approach (e.g., two or more tags) may be defined for MEC resource characterization for MEC planning, handover, and migration, including profile generation. Performance characterization may include channel conditions, including Doppler, to characterize the rate of change of location and predict new locations.
[0136] The first label of the multi-label method can be associated with the TSN configuration and schedule the data processed at the MEC processing system. When assigning this label, the MEC processing system can convert the unbounded latency of the processed data into bounded latency. In some embodiments, the MEC processing system can assign this label based on the deadline-based latency requirements.
[0137] A second tag of the multi-tag approach may be associated with core resource allocation. Example metrics underlying this tag include one or more of the following: (1) MIPS math functions (e.g., FFT, logic, multiply-accumulate, etc.), and / or metrics related to processing, such as available memory, available processing resources, and / or duty cycles; (2) Kolmogorov complexity metrics (e.g., algorithmic information theory); (3) active network timing metrics (e.g., compression and transmission of processing algorithms from one MEC to another); and / or (4) metrics related to benchmark application classifications (thereby standardizing metrics across applications).
[0138] In some implementations, the multi-tag approach described above can adapt to time-varying application requirements (e.g., profile adaptation). While TSN can be configured to adapt to application and processing requirements, the MEC resource characterization scheme described herein can additionally or alternatively take into account application and processing speeds as they react to network requirements, which are in a more symmetrical and dynamic relationship with network requirements.
[0139] The MEC resource characterization scheme described herein enables better performance and optimization of 5G systems for real-time control applications. Thus, a 5G wireless engine control system (e.g., distributed FADEC) can be placed entirely within the MEC and communicate in real time with a user device (e.g., a car or aircraft) via 5G. In one example, a MEC application may include multiple interactive MEC processes that can quickly interact with the user device to maintain efficient performance.
[0140] The UE / MEC application network topology as described herein enables MEC applications to migrate at a rate proportional to the UE changes of the MEC (referred to as the MEC migration speed) based on the aforementioned MEC performance characterization (in other words, based on the performance characterization metric).
[0141] In some embodiments, MEC migration velocity is an abstract concept that includes application flow bandwidth, determinism, paths, and changes in the location of MEC applications within a network graph representing the link interconnection topology.
[0142] The MEC processor must be able to support the required computations, and therefore will also expose performance characterization metrics that represent determinism as a function of the load on the MEC processing system. Processing determinism may decrease as the load increases because the overhead required to manage the load interferes with the main computations. Given such curves, the 5GS can better decide how to manage traffic flow rates (TSN) and processing rates (MEC applications) to achieve the desired performance, possibly through the methods already described in this disclosure (MIPS, Kolmogorov complexity, etc.). Specifically, based on the performance characterization metrics, the 5GS can determine when to migrate MEC applications, when to throttle traffic, when to adjust processing speed to maintain determinism and not overflow the network, and / or when to expand MEC processing capabilities (e.g., add more / faster processors or separate applications across more processors).
[0143] Therefore, in an exemplary communication system including a core network, a radio access network communicatively coupled to the core network, and an MEC processing system communicatively coupled to the radio access network, the MEC processing system includes one or more processors and a memory storing one or more programs to be executed by the one or more processors, the one or more programs including instructions for the following operations: (i) determining a performance characterization metric representing a determinism that varies with the load of the MEC processing system; and (ii) adjusting the traffic flow rate of a time sensitive network (TSN) of the radio access network based on the performance characterization metric.
[0144] In some embodiments, the instructions for determining a performance characterization metric include instructions for: labeling data processed by the MEC processing system with a first tag corresponding to one or more TSN configuration and scheduling metrics; and determining the performance characterization metric based on the first tag.
[0145] In some embodiments, the instructions for determining a performance characterization metric include instructions for: labeling data processed by the MEC processing system with a second tag corresponding to one or more resource allocations from the core network; and determining the performance characterization metric based on the second tag.
[0146] In some embodiments, the instructions for labeling data with a second label include instructions for: determining MIPS, memory, processing and / or duty cycle metrics associated with the core network; and assigning the second label based on the MIPS, memory, processing and / or duty cycle metrics.
[0147] In some embodiments, the instructions for labeling the data with the second label include instructions for: determining a Kolmogorov complexity metric associated with the core network; and assigning the second label based on the Kolmogorov complexity metric.
[0148] In some embodiments, the instructions for labeling the data with the second label include instructions for: determining an active network timing metric associated with the core network; and assigning the second label based on the active network timing metric.
[0149] In some embodiments, the instructions for labeling the data with the second label include instructions for: determining a resource allocation metric associated with the core network; comparing the resource allocation metric to a benchmark metric; and assigning the second label based on the comparison.
[0150] In some embodiments, the instructions for labeling data with the first tag and / or the second tag include instructions for: detecting time-varying requirements of the MEC processing system; and assigning the first tag and / or the second tag based on the time-varying requirements.
[0151] In some embodiments, the instructions for determining a performance characterization metric include instructions for annotating data processed by the MEC processing system.
[0152] In some embodiments, the one or more programs further include instructions for: executing the MEC application; and determining whether to migrate the MEC application to the second MEC processing system based on the performance characterization metric. For example, the system determines whether to migrate the MEC application to the second MEC processing system based on a comparison of the performance characterization metrics corresponding to each of the plurality of second edge-enabled devices (e.g., evaluating Fig.11 The system determines which edge-enabled device (e.g., an MEC processing system) of the plurality of second edge-enabled devices to which the application will be migrated based on the performance characterization metrics of the plurality of DUs 1104 in the system. In some embodiments, the system assigns one of the plurality of second edge-enabled devices to continue executing the application based on the determination (e.g., selecting the DU 1104 with the best performance characterization metric), migrates the application to the assigned edge-enabled device, and continues to execute the application on the assigned edge-enabled device according to the TSN configuration of the assigned edge-enabled device.
[0153] In some embodiments, the one or more programs further include instructions for: executing the MEC application; and adjusting a processing rate of the MEC application based on the performance characterization metric.
[0154] In some embodiments, instructions for adjusting the processing rate of the MEC application include instructions for scaling or throttling MEC processing services.
[0155] In some embodiments, the one or more programs further include instructions for determining whether to adjust processing traffic at the MEC processing system based on the performance characterization metric to maintain the deterministic threshold and not overflow the radio access network.
[0156] other
[0157] The above description has been described with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the claims to the precise forms disclosed. In view of the above teachings, many variations are possible. In order to best explain the operating principles and practical applications, the embodiments have been selected and described, thereby inspiring other technical personnel in the field.
[0158] The various figures show multiple elements in a particular order. However, elements that are not order-dependent may be reordered, and other elements may be combined or separated. Although some reorderings or other groupings are specifically mentioned, other reorderings or groupings are obvious to those of ordinary skill in the art, and thus the orderings and groupings presented herein are not an exhaustive list of alternatives.
[0159] As used herein: the singular forms "a", "an" and "the" also include the plural forms, unless the context clearly indicates otherwise; the term "and / or" covers all possible combinations of one or more of the associated listed items; the terms "first", "second", etc. are only used to distinguish one element from another, and do not limit the elements themselves; depending on the context, the term "if" can be interpreted as "when", "based on", "in response to" or "according to"; and the terms "include", "including", "comprise" and "comprising" indicate specific features or operations, but do not exclude additional features or operations.
Claims
1. A communication system, comprising: Core network; as well as a radio access network comprising a central unit (i) communicatively coupled to the core network via a backhaul network and (ii) communicatively coupled to a plurality of distributed units via a fronthaul network; wherein each of the plurality of distributed units is co-located with a radio frequency unit and includes an edge enabling device; wherein the edge-enabled device of each of the plurality of distributed units comprises a communication data link, one or more processors, and a memory storing one or more programs to be executed by the one or more processors, the one or more programs comprising instructions for: Control deterministic network configuration; executing one or more applications according to the deterministic network configuration; determining a performance characterization metric representing processing time, system latency, available capacity, available load, user equipment speed, and / or processing determinism as a function of load on the edge-enabled device; as well as Deterministic network traffic of the radio access network is adjusted based on the performance characterization metric.
2. The communication system of claim 1, wherein the edge-enabled device of each of the plurality of distributed units is directly connected to the fronthaul network.
3. The communication system of claim 2, wherein the instructions for executing the one or more applications include instructions for: Data is transmitted and received via the fronthaul network according to the deterministic network configuration.
4. The communication system of claim 1 , wherein the instructions for executing the one or more applications include instructions for: Analog user data associated with the co-located radio frequency unit is processed.
5. The communication system according to claim 4, wherein: The user data is encoded in an in-phase and quadrature (I / Q) signal; and The instructions for processing the analog user data include instructions for processing the I / Q signals according to one or more homomorphic processing functions.
6. The communication system of claim 1, wherein the instructions for executing the one or more applications include instructions for: executing a service on a first distributed unit among the plurality of distributed units; determining that a user device associated with the service is moving from a service area of the first distributed unit to a service area of a second distributed unit among the plurality of distributed units; and Based on the determination that the user device is moving from the service area of the first distributed unit to the service area of the second distributed unit, the service is migrated to the second distributed unit.
7. The communication system of claim 6, wherein the instructions for migrating the service to the second distributed unit include instructions for: Integration of the service with the fronthaul network is maintained while migrating the service to the second distributed unit.
8. The communication system of claim 6, wherein the instructions for migrating the service to the second distributed unit include instructions for: converting the one or more applications into deterministic network flows; The deterministic network flow is migrated from an edge-enabled device of the first distributed unit to an edge-enabled device of the second distributed unit.
9. The communication system of claim 6, wherein the instructions for migrating the service to the second distributed unit include instructions for: The service is migrated via the fronthaul network according to a deterministic flow.
10. The communication system according to any one of claims 6 to 9, wherein the service is a deterministic message flow service.
11. The communication system of any one of claims 1 to 10, wherein the one or more applications are vehicle engine control applications configured to send and receive engine control data to and from an aircraft or automobile within a service area of one or more of the plurality of distributed units.
12. A communication system according to any one of claims 1 to 10, wherein the one or more applications are grid monitoring and control applications, which are configured to send control data to and receive control data from a grid infrastructure within a service area of one or more of the plurality of distributed units.
13. The communication system according to any one of claims 1 to 12, wherein the edge-enabled device is a multi-access edge computing (MEC) device.
14. The communication system according to any one of claims 1 to 13, wherein the deterministic network configuration is a time sensitive network (TSN) configuration.
15. The communication system according to any one of claims 1 to 14, wherein the one or more programs further comprise instructions for: determining a performance characterization metric representing processing time, system latency, available capacity, available load, user equipment speed, and / or processing determinism as a function of load on the edge-enabled device; and Deterministic network traffic of the radio access network is adjusted based on the performance characterization metric.
16. The communication system of claim 15, wherein the performance characterization metric is determined based on one or more deterministic network configuration and scheduling metrics.
17. The communication system of claim 15, wherein the performance characterization metric is determined based on one or more resource allocations from the core network.
18. The communication system of claim 17, wherein the performance characterization metric is determined based on a MIPS, memory, processing and / or duty cycle metric associated with the core network.
19. The communication system of claim 17, wherein the performance characterization metric is determined based on a Kolmogorov complexity metric associated with the core network.
20. The communication system of claim 17, wherein the performance characterization metric is determined based on an active network timing metric associated with the core network.
21. The communication system of claim 17, wherein the performance characterization metric is determined based on a comparison of (i) a resource allocation metric associated with the core network and (ii) a benchmark metric.
22. The communication system of any one of claims 16 to 21, wherein the performance characterization metric is determined based on time-varying requirements of the edge-enabled device.
23. The communication system of any one of claims 15 to 22, wherein the performance characterization metric is determined based on data processed by the edge-enabled device.
24. The communication system of any one of claims 15 to 23, wherein the one or more programs further include instructions for: Execute the application; and Based on a comparison of the performance characterization metrics corresponding to each of the plurality of second edge-enabled devices, a determination is made as to which edge-enabled device of the plurality of second edge-enabled devices to migrate the application.
25. The communication system of claim 24, wherein the one or more programs further include instructions for: assigning one of the plurality of second edge-enabled devices to continue executing the application based on the determination; and The application is executed on the assigned edge-enabled device according to the deterministic network configuration of the assigned edge-enabled device.
26. The communication system of any one of claims 15 to 25, wherein the one or more programs further include instructions for: Execute the application; and A processing rate of the application is adjusted based on the performance characterization metric.
27. The communication system of claim 26, wherein the instructions for adjusting the processing rate of the application program include instructions for scaling or throttling processing traffic associated with the edge-enabled device.
28. The communication system of any one of claims 15 to 27, wherein the one or more programs further include instructions for determining whether to adjust processing traffic at the edge-enabled device to maintain a deterministic threshold and not overflow the radio access network based on the performance characterization metric.
29. A communication system comprising: Core network; as well as a radio access network comprising a central unit (i) communicatively coupled to the core network via a backhaul network and (ii) communicatively coupled to a plurality of distributed units via a fronthaul network; wherein each of the plurality of distributed units is co-located with a radio frequency unit and includes an edge enabling device; wherein the edge-enabled device of each of the plurality of distributed units comprises a communication data link, one or more processors, and a memory storing one or more programs to be executed by the one or more processors, the one or more programs comprising instructions for: Controlling deterministic network configuration using a Representational State Transfer Application Programming Interface (RESTful API); and One or more applications are executed according to the deterministic network configuration.
30. A method of operating a communication system, the method comprising one or more of the operations according to any one of claims 1 to 29.
