| |
Table 6.22.2.2-1 | Access Identities |
Table 6.22.2.3-1 | Access Categories |
Figure 6.37.1-1 | Illustration of ranging between UEs with or without 5G coverage |
Figure 6.43.1-1 | Multi-modal interactive system |
Table 6.43.1-1 | Typical synchronization thresholds for immersive multi-modality VR applications |
Table 7.1-1 | Performance requirements for high data rate and traffic density scenarios |
Table 7.2.3.2-1 | Performance requirements for wireless ITS infrastructure backhaul scenario |
Table 7.3.2.2-1 | Performance requirements for Horizontal and Vertical positioning service |
Table 7.4.1-1 | Propagation delay via satellite |
Table 7.4.2-1 | Performance requirements for satellite access |
Table 7.5.2-1 | Performance requirements for highly reliable machine type communication |
Table 7.6.1-1 | KPI Table for additional high data rate and low latency service |
Table 7.7-1 | Key Performance for UE to network relaying |
Table 7.8-1 | Timing resiliency performance requirements for 5G System |
Table 7.8-2 | Timing resiliency accuracy KPIs for members or participants of a trading venue [35] |
Table 7.9-1 | Performance requirements for ranging based services |
Table 7.10.1-1 | KPI Table of split AI/ML inference between UE and Network Server/Application function |
Table 7.10.1-2 | KPI Table of AI/ML model downloading |
Table 7.10.1-3 | KPI Table of Federated Learning between UE and Network Server/Application function |
Table 7.10.2-1 | KPI Table of Split AI/ML operation between AI/ML endpoints for AI inference by leveraging direct device connection |
Table 7.10.2-2 | KPI Table of AI/ML model/data distribution and sharing by leveraging direct device connection |
Table 7.10.2-3 | KPI Table of Distributed/Federated Learning by leveraging direct device connection |
Table 7.11-1 | Multi-modal communication service performance requirements |
Table 7.12-1 | Key Performance for UE to UE relaying for Public Safety |
Table 7.13-1 | Performance requirements for energy-related characteristics exposure |
Figure D.1.0-1 | Communication path for isochronous control cycles within factory units. Step 1 (red): controller requests sensor data (or an actuator to conduct actuation) from the sensor/actuator (S/A). Step 2 (blue): sensor sends measurement information (or acknowledges actuation) to controller. |
Figure D.2.0-1 | Communication path for service flows between process controllers and sensor/actuator devices. Left-hand side: Step 1 (red) - the sensor/actuator (S/A) sends measurement report autonomously, Step 2 (blue) controller acknowledges. Right-hand side: Step 1 (red) - controller requests sensor data (or an actuator to conduct actuation), Step 2 (blue): S/A sends measurement information (or acknowledges actuation) to controller. |
Figure D.4.1.0-1 | Functional, topological sketch of a medium-voltage ring. AMI: advanced metering infrastructure; CB: circuit breaker; DMS: distribution management system; FISR: fault isolation and system restoration; HEM: home energy manager; PQ: power quality; RMU: ring main unit. |
Figure F.1-1 | QoS assurance by use of QoS monitoring information |
Table G.2-1 | Battery life expectancy and message size to support example use cases for asset tracking |
Figure H-1 | Home Operator owned/collaborative interworking scenario Home Routed |
Figure H-2 | Hosting Network Operator owned/collaborative interworking scenario Local Breakout |
Figure I-1 | Different options both direct and indirect connections between the Shared NG-RAN and the core networks of the participating operators. |
Figure I-2 | Indirect Network Sharing scenario involving core network of Hosting NG-RAN Operator between the Shared NG-RAN and the core networks of the participating operators. |
Figure J-1 | Illustration of "normal/default operation" and "S&F Satellite operation" modes in a 5G system with satellite access |