Content for TR 22.832 Word version: 17.4.0
6 Merged potential service requirements
7 Conclusions
A Considerations on communication service interface
B Considerations on absolute and relative positioning
C Industrial communication network architecture
D Communication service availability vs. failure
E Requirements mapping use case to merged
$ Change history
6 Merged potential service requirements p. 60
6.1 Industrial Ethernet integration p. 60
6.2 Non-public networks p. 61
6.3 Network operation and Maintenance p. 61
6.4 Network performance requirements p. 62
6.5 Positioning p. 67
6.6 Device-to-device/ProSe communication p. 68
7 Conclusions p. 69
A Considerations on communication service interface p. 70
A.1 Overview p. 70
A.2 Classification of Application Requirements p. 70
A.2.1 Characteristic parameters for identification of requirement classes p. 71
A.2.2 Descriptive parameters (Dsp) p. 71
A.2.3 Quality of Service Parameters (QoSp) p. 71
A.3 Requirement classification p. 71
A.3.1 Deterministic Periodic p. 71
A.3.2 Deterministic Aperiodic p. 72
A.3.3 Non-Deterministic p. 72
A.3.4 Real-time and Non-Real-time Classification p. 72
A.3.5 Other Classifications. p. 72
A.4 General Use Case for Communication Service Interface p. 72
A.4.1 General Consideration p. 72
A.4.2 Pre-conditions p. 73
A.4.3 Service Flows p. 73
A.4.4 Post-conditions p. 74
A.5 Requirements on Communication Service Interface p. 74
A.5.1 Output block p. 74
A.5.2 Input block p. 74
A.5.3 Communication Service Interface consideration for 5G Systems p. 74
A.5.4 General application & communication service interface format p. 75
A.6 Communication Service objectives and candidate parameters p. 75
B Considerations on absolute and relative positioning p. 78
C Industrial communication network architecture p. 80
C.1 Overview p. 80
C.2 Use Case 1: Line Controller-to-Controller (L2C) and Controller-to-Controller (C2C) communication p. 80
C.3 Use Case 2: Controller-to-Device (C2D) communication p. 81
C.4 Use Case 3: Device to Compute (D2Cmp) Communication p. 81
D Communication service availability vs. failure p. 83
E Requirements mapping use case to merged p. 85
$ Change history p. 86
