Content for TR 23.745 Word version: 17.0.0
4 Analysis of existing standards
5 Key issues
6 Architectural requirements
7 Solutions
8 Overall evaluation
9 Conclusions
A Analysis of relationship between oneM2M and FF architecture
B Integration with Operation Technologies
C Analysis of relationship between OPC UA and FF architecture
D Deployment Models
$ Change history
4 Analysis of existing standards p. 11
4.1 Analysis of TS 22.261 p. 11
4.1.1 Description p. 11
4.1.2 Analysis p. 11
4.2 Analysis of TS 22.104 p. 12
4.2.1 Description p. 12
4.2.2 Analysis p. 12
5 Key issues p. 13
5.1 Key issue 1 - Use of network slicing for FFAPP p. 13
5.2 Key issue 2 - Geographic location and positioning information support p. 14
5.3 Key issue 3 - Clock synchronization p. 14
5.4 Key issue 4 - TSN supporting p. 14
5.5 Key issue 5 - QoS monitoring p. 15
5.6 Key issue 6 - 5GLAN group management p. 16
5.7 Key Issue 7 - Device Onboarding p. 17
5.8 Key issue 8 - Communication of FF application requirements with 5GS p. 17
5.9 Key issue 9 - Communication service on the Edge deployments p. 18
5.10 Key issue 10 - Integration with Existing Operation Technologies p. 18
5.11 Key issue 11 - QoS coordination p. 18
5.12 Key Issue 12 - User authorization p. 19
5.13 Key Issue 13: Capability Exposure related to Private Slice Network Status p. 19
5.14 Key Issue 14 - Device monitoring p. 19
5.15 Key Issue 15 - Support for group communication p. 19
5.16 Key Issue 16 - Constrained devices p. 20
5.17 Key Issue 17 - Using 5G CN capabilities for SEAL Groups p. 20
5.18 Key Issue 18 - Support for Message communication p. 20
6 Architectural requirements p. 21
6.1 General requirements p. 21
6.1.1 Description p. 21
6.1.2 Requirements p. 21
6.2 Requirements for supporting time sensitive communication services p. 21
6.2.1 Description p. 21
6.2.2 Requirements p. 21
7 Solutions p. 22
7.1 Solution #1: FF application layer functional model p. 22
7.1.1 Solution description p. 22
7.1.1.1 General p. 22
7.1.1.2 FF application layer functional model p. 22
7.1.1.3 Functional entities description p. 23
7.1.1.3.1 General p. 23
7.1.1.3.2 FF application specific client p. 23
7.1.1.3.3 FF application specific server p. 24
7.1.1.3.4 FAE client p. 24
7.1.1.3.5 FAE server p. 24
7.1.1.3.6 SEAL client p. 24
7.1.1.3.7 SEAL server p. 24
7.1.1.4 Reference points p. 25
7.1.1.4.1 General p. 25
7.1.1.4.2 FAE-1 p. 25
7.1.1.4.3 FFA-1 p. 25
7.1.1.4.4 FAE-E p. 25
7.1.1.4.5 FAE-S p. 25
7.1.1.4.6 FAE-C p. 25
7.1.1.4.7 SEAL-C p. 25
7.1.1.4.8 SEAL-S p. 25
7.1.1.5 External reference points p. 26
7.1.2 Solution evaluation p. 26
7.2 Solution #2: Establishing communication with FF application service requirements p. 26
7.2.1 Solution description p. 26
7.2.2 Solution evaluation p. 28
7.3 Solution #3: Support UE to UE direct communication in FF application layer p. 28
7.3.1 Solution description p. 28
7.3.2 Solution evaluation p. 28
7.4 Void
7.5 Solution #5: Edge deployment within FFAPP p. 28
7.5.1 Solution description p. 28
7.5.2 Solution evaluation p. 29
7.6 Solution #6: Provisioning of FFAPP within Edge Data Network configuration p. 29
7.6.1 Solution description p. 29
7.6.2 Solution evaluation p. 29
7.7 Solution #7 Geographic location and positioning information support p. 29
7.7.1 General p. 29
7.7.2 Usage of SEAL location management Information flows p. 29
7.7.3 Usage of SEAL location management procedures p. 30
7.7.4 Enhancements to SEAL location management Information flows p. 30
9.2.2 On-network functional model description p. 32
9.3.8 Event-trigger location information notification procedure p. 33
9.3.9 On-demand usage of location information procedure p. 33
7.7.5 Solution evaluation p. 34
7.8 Solution #8: QoS monitoring p. 34
7.8.1 Solution description p. 34
7.8.2 Solution evaluation p. 35
7.9 Solution #9: 5GLAN group management p. 36
7.9.1 Solution description p. 36
7.9.1.1 General p. 36
7.9.1.2 Information flows p. 36
7.9.1.3 Procedures p. 38
7.9.1.4 Required SEAL group management enhancements p. 38
7.9.1.5 5GLAN group creation and join procedure p. 38
7.9.2 Solution evaluation p. 40
7.10 Solution #10: QoS monitoring for TSC services p. 40
7.10.1 Solution description p. 40
7.10.2 Subscribe/unsubscribe to/from QoS monitoring events for an established connection p. 41
7.10.3 Solution evaluation p. 42
7.11 Solution #11: Establishing communication connectivity between FF Application Specific Clients with FF application service requirements p. 42
7.12 Solution #12: Private Slice p. 44
7.12.1 Solution description p. 44
7.12.1.1 General p. 44
7.12.1.2 Acquirement of private slice network status information procedure p. 45
7.12.2 Solution evaluation p. 46
7.13 Solution #13: Application-triggered slice re-mapping for FF applications p. 46
7.13.1 Solution description p. 46
7.13.1.1 General p. 47
7.13.1.2 Procedure p. 47
7.13.2 Solution evaluation p. 48
7.14 Solution #14 clock synchronization p. 48
7.15 Solution 15: Time Synchronization Management p. 48
7.15.1 Time Synchronization support p. 48
7.15.2 Time Synchronization activation/deactivation/modification p. 49
7.15.3 Solution evaluation p. 50
7.16 Solution #16: TSN policy negotiation via FAE layer p. 50
7.16.1 Solution description p. 50
7.16.1.1 General p. 51
7.16.1.2 Procedure p. 51
7.16.2 Solution evaluation p. 52
7.17 Solution #17: Support TSN in FF Application Enabler layer p. 52
7.18 Solution #18: Device monitoring p. 53
7.18.1 Solution description p. 53
7.18.1.1 General p. 53
7.18.1.2 Device monitoring procedure p. 54
7.18.2 Solution evaluation p. 55
7.19 Solution #19: Communicating FF application service requirements with 3GPP system p. 55
7.20 Solution #20: SEAL support for CoAP to address constrained devices p. 55
7.20.1 Solution description p. 55
7.20.1.1 Introduction p. 55
7.20.2 SEAL functional model for signalling control plane including CoAP p. 56
7.20.3 CoAP entities p. 57
7.20.4 Signalling control plane reference points for CoAP p. 58
7.20.4.1 Reference point CoAP-1 (between the CoAP client and the CoAP proxy) p. 58
7.20.4.2 Reference point CoAP-2 (between the CoAP proxy and the CoAP server) p. 58
7.20.4.3 Reference point CoAP-3 (between the CoAP proxy and CoAP proxy) p. 58
7.20.5 CoAP usage p. 58
7.20.6 Solution evaluation p. 58
7.21 Solution #21: Enabling 5G CN capabilities for SEAL Groups p. 58
7.21.1 Solution description p. 58
7.21.2 SEAL Group creation procedures p. 59
7.21.3 Solution evaluation p. 61
7.22 Solution #22: SEAL support for TSC services p. 61
7.22.1 Introduction p. 61
7.22.2 Solution description p. 61
7.22.3 5G-native TSC procedures p. 63
7.22.3.1 TSC stream discovery procedure p. 63
7.22.3.2 TSC stream creation procedure p. 64
7.22.3.3 Void
7.22.3.4 Void
7.22.3.5 TSC stream deletion procedure p. 65
7.22.4 IEEE-TSN TSC procedures p. 66
7.22.4.1 5GS TSN Bridge information reporting p. 66
7.22.4.2 5GS TSN Bridge configuration procedure p. 66
7.22.5 Solution evaluation p. 67
7.23 Solution #23 (merging Sol#5, #6): Edge computing for FFAPP p. 67
7.24 Solution #24: Message communication using MSGin5G service p. 69
8 Overall evaluation p. 69
8.1 General p. 69
8.2 Architecture evaluation p. 70
8.3 Key issue and solution evaluation p. 70
8.3.1 General p. 70
8.3.2 Overall evaluation of solutions for key issue#1 p. 72
8.3.3 Overall evaluation of solutions for key issue#2 p. 72
8.3.4 Overall evaluation of solutions for key issue#3 p. 73
8.3.5 Overall evaluation of solutions for key issue#4 p. 73
8.3.6 Overall evaluation of solutions for key issue#5 p. 73
8.3.7 Overall evaluation of solutions for key issue#6 p. 74
8.3.8 Overall evaluation of solutions for key issue#7 p. 74
8.3.9 Overall evaluation of solutions for key issue#8 p. 74
8.3.10 Overall evaluation of solutions for key issue#9 p. 75
8.3.11 Overall evaluation of solutions for key issue#10 p. 75
8.3.12 Overall evaluation of solutions for key issue#11 p. 75
8.3.13 Overall evaluation of solutions for key issue#12 p. 76
8.3.14 Overall evaluation of solutions for key issue#13 p. 76
8.3.15 Overall evaluation of solutions for key issue#14 p. 76
8.3.16 Overall evaluation of solutions for key issue#15 p. 76
8.3.17 Overall evaluation of solutions for key issue#16 p. 76
8.3.18 Overall evaluation of solutions for key issue#17 p. 77
8.3.19 Overall evaluation of solutions for key issue#18 p. 77
9 Conclusions p. 77
A Analysis of relationship between oneM2M and FF architecture p. 79
B Integration with Operation Technologies p. 80
B.1 Overview p. 80
C Analysis of relationship between OPC UA and FF architecture p. 80
C.1 Overview p. 80
D Deployment Models p. 82
D.1 General p. 82
D.2 FAE/SEAL Server deployment in PLMN/NPN operator domain p. 82
D.3 FAE/SEAL Server deployment at FAE/SEAL service provider domain p. 83
D.4 FAE/SEAL Server deployment at FF application service provider domain p. 83
$ Change history p. 85
