| |
Figure 5.1-1 | Network perspective of 5G system |
Table 5.1-1 | Example of relationship between reliability (as defined in TS 22.261) and communication service availability when the survival time is equal to the transfer interval |
Table 5.2-1 | Periodic deterministic communication service performance requirements |
Table 5.2-2 | Communication service performance requirements for industrial wireless sensors |
Table 5.3-1 | Aperiodic deterministic communication service performance requirements |
Table 5.4-1 | Non-deterministic communication service performance requirements |
Table 5.5-1 | Mixed traffic communication service performance requirements |
Table 5.6.2-1 | Clock synchronization service performance requirements for 5G System |
Table 5.7.1-1 | Positioning performance requirements |
Table 7.2.3.2-1 | Direct device connection clock synchronization service performance requirements for 5G System |
Table 8.2.3.2-1 | Indirect network connection clock synchronization service performance requirements for 5G System |
Table A.2.1-1 | Mapping of the considered use cases (columns) to application areas (rows) |
Figure A.2.2.1-1 | Schematic representation of a motion control system |
Table A.2.2.1-1 | Service performance requirements for motion control |
Table A.2.2.2-1 | Service performance requirements for control-to control communication in motion control |
Table A.2.2.3-1 | Service performance requirements for mobile robots |
Figure A.2.2.4-1 | Example of four cooperating machines with wireless connections (based on [26]) |
Table A.2.2.4-1 | Service performance requirements for wired to wireless link replacement |
Figure A.2.2.5-1 | Mobile robots / AGVs carrying a large work piece cooperatively |
Table A.2.2.5-1 | Service performance requirements for cooperative carrying |
Table A.2.3.1-1 | Service performance requirements for closed-loop control in process automation |
Table A.2.3.2-1 | Service performance requirements for process and asset monitoring |
Table A.2.3.3-1 | Service performance requirements for plant asset management |
Table A.2.3.4 | Service performance requirements for automated inspection |
Figure A.2.3.4-1 | |
Table A.2.4.1-1 | Service performance requirements for mobile control panels |
Table A.2.4.1A-1 | Service performance requirements for mobile operation panels |
Table A.2.4.2-1 | Service performance requirements for augmented reality in human-machine interfaces |
Table A.2.5.1-1 | Service performance requirements for remote access and maintenance |
Table A.4.2-1 | Service performance requirements for primary frequency control |
Table A.4.3-1 | Service performance requirements for distributed voltage control |
Figure A.4.4.1-1 | Depiction of a distribution ring and a failure (flash of lighting) |
Table A.4.4.1-1 | Service performance requirements for distributed automated switching for isolation and service restoration |
Table A.4.4.2-1 | KPI for distributed automation without use of GOOSE |
Figure A.4.4.3-1 | Example of intelligent distributed feeder automation |
Table A.4.4.3-1 | KPI for intelligent distributed feeder automation |
Table A.4.4.4-1 | KPIs for high speed current differential protection |
Table A.4.5-1 | Service performance requirements for smart grid millisecond-level precise load control |
Figure A.4.6-1 | Example of a distributed-energy storage grid |
Table A.4.6-1 | Communication service performance requirements - data for distributed energy storage |
Table A.4.7-1 | Communication KPI for advanced metering |
Figure A.4.8-1 | Example of a smart distribution transformer terminal workflow |
Table A.4.8-1 | Key Performance for Smart Distribution Transformer Terminal |
Table A.4.9-1 | Key Performance for Distributed energy resources (DER): using SV (Sampled Values) message |
Table A.4.10-1 | Key Performance for uninterrupted MTC service availability |
Table A.5.2-1 | Service performance requirements for wind power plant network |
Figure A.6.2-1 | Typical Robotic Surgery System Setup |
Table A.6.2-1 | Service performance requirements for motion control and haptic feedback |
Figure A.6.3-1 | Typical Robotic Surgery System Setup |
Table A.6.3-1 | Service performance requirements for motion control and haptic feedback |
Table A.7.2-1 | Low power high accuracy positioning use cases |
Figure C.1.1-1 | Abstract diagram of the area of consideration for industrial radio communication |
Figure C.1.2.1-1 | The concept of a logical link |
Figure C.1.2.1-2 | The asset "logical link" |
Table C.1.2.2-1 | Partition into higher communication layer and lower communication layer |
Figure C.1.2.3-1 | Asset "communication device" |
Table C.2.2-1 | Candidate characteristic parameters for the dependable communication service interface |
Table C.2.3-1 | Candidate application influencing parameters for the dependable communication service interface |
Figure C.3-1 | Relation between logical communication link, communication service and application statuses (example with lost messages) |
Figure C.4.3-1 | Timeliness function |
Figure C.4.4-1 | Examples for accuracy values |
Figure C.4.4-2 | Accuracy function |
Figure C.4.5-1 | Earliness function |
Figure C.4.6-1 | Lateness function |
Figure C.5-1 | Network performance measurements at different communication system interfaces (CSIF) |
Figure C.5-2 | Relation between application device and communication device (downlink example). |
Figure D.1-1 | Global time domain and working clock domains |
Figure D.2-1 | Working clock domain interactions "Merge" and "Separate" |
Figure E.2-1 | Typical AVPROD setup |
Figure E.3-1 | Typical IP based timing set up for AVPROD |
Figure F-1 | Illustration of the concepts reliability and communication service availability. |
Figure F-2 | Example in which reliability and communication service availability have different values. Packets are reliably transmitted from the communication service interface A to end node B, but they are not exposed at the communication service interface B. |
Figure F-3 | Example in which reliability and communication service availability have different values. Only half of the packets handed over to the end node A are actually transmitted to end node B and then handed over to application B at the communication service interface B. |