C.3 Support for FF message delivery by SEALDD
23.5453GPPApplication layer support for Factories of the Future (FF)Release 18TS
Editor’s note: the content shall be cross-checked, and if needed aligned with the final version of SEALDD later.
C.3.1 General
The FF application layer utilizes the SEAL services to support for FF message delivery by SEALDD specified in 3GPP TS 23.433 [11].
C.3.2 SEALDD regular connection establishment
The SEALDD regular connection establishment procedures are specified in subclause 9.2 of 3GPP TS 23.433 [11].
The following information flows applied:
– SEALDD enabled regular transmission request specified in subclause 9.2.3.1 of 3GPP TS 23.433 [11];
– SEALDD enabled regular transmission response specified in subclause 9.2.3.2 of 3GPP TS 23.433 [11];
– SEALDD enabled regular transmission connection establishment request specified in subclause 9.2.3.3 of 3GPP TS 23.433 [11];
– SEALDD enabled regular transmission connection establishment response specified in subclause 9.2.3.4 of 3GPP TS 23.433 [11];
C.3.3 SEALDD enabled E2E redundant transmission
The SEALDD enabled E2E redundant transmission procedure is specified in subclause 9.3 of 3GPP TS 23.433 [11].
The following information flows applied:
– SEALDD URLLC transmission request specified in subclause 9.3.3.1 of 3GPP TS 23.433 [11];
– SEALDD URLLC transmission response specified in subclause 9.3.3.2 of 3GPP TS 23.433 [11];
– SEALDD URLLC transmission connection establishment request specified in subclause 9.3.3.3 of 3GPP TS 23.433 [11];
– SEALDD URLLC transmission connection establishment response specified in subclause 9.3.3.4 of 3GPP TS 23.433 [11];
– SEALDD URLLC transmission connection update request specified in subclause 9.3.3.5 of 3GPP TS 23.433 [11];
– SEALDD URLLC transmission connection update response specified in subclause 9.3.3.6 of 3GPP TS 23.433 [11];
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2021-10 |
SA6#45-BIS-e |
TS skeleton |
0.0.0 |
||||
|
2021-10 |
SA6#45-BIS-e |
Implementation of the following pCRs approved by SA6: S6-212389, S6-212234, S6-212468 |
0.1.0 |
||||
|
2021-11 |
SA6#46-e |
Implementation of the following pCRs approved by SA6: S6-212822, S6-212741, S6-212532 |
0.2.0 |
||||
|
2022-02 |
SA6#47-e |
Implementation of the following pCRs approved by SA6: S6-220403, S6-220323, S6-220442, S6-220061 |
0.3.0 |
||||
|
2022-04 |
SA6#48-e |
Implementation of the following pCRs approved by SA6: S6-220936, S6-220886 |
0.4.0 |
||||
|
2022-05 |
SA6#49-e |
Implementation of the following pCRs approved by SA6: S6-221283,S6-221018, S6-221284 |
0.5.0 |
||||
|
2022-07 |
SA6#49-Bis-e |
Implementation of the following pCRs approved by SA6: S6-221906 |
0.6.0 |
||||
|
2022-10 |
SA6#51-e |
Implementation of the following pCRs approved by SA6: S6-223031, S6-222896 |
0.7.0 |
||||
|
2022-11 |
SA6#52 |
Implementation of the following pCRs approved by SA6: S6-223559 |
0.8.0 |
||||
|
2023-01 |
SA6#52-Bis-e |
Implementation of the following pCRs approved by SA6: S6-230455, S6-230456 |
0.9.0 |
||||
3GPP TS 23.545 V0.9.0 (2023-01)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Application layer support for Factories of the Future (FF);
(Release 18)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners’ Publications Offices.
3GPP
Postal address
3GPP support office address
650 Route des Lucioles – Sophia Antipolis
Valbonne – FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Intpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
Contents
Foreword 6
Introduction 6
1 Scope 7
2 References 7
3 Definitions, symbols and abbreviations 7
3.1 Definitions 7
3.2 Symbols 8
3.3 Abbreviations 8
4 Architectural requirements 8
4.1 General 8
4.1.1 Description 8
4.1.2 Requirements 8
4.2 <Requirement type x> 9
4.2.1 Description 9
4.2.2 Requirements 9
5 Application layer architecture 9
5.1 General 9
5.2 Architecture 9
5.3 Functional entities 12
5.3.1 General 12
5.3.2 FF application specific client 12
5.3.3 FF application specific server 12
5.3.4 FAE client 12
5.3.5 FAE server 12
5.3.6 SEAL client 12
5.3.7 SEAL server 13
5.4 Service-based interfaces 13
5.5 Reference Points 13
5.5.1 General 13
5.5.2 FAE-1 13
5.5.3 FFA-1 13
5.5.4 FAE-2 13
5.5.5 FFA-2 13
5.5.6 FAE-S 14
5.5.7 FAE-C 14
5.5.8 SEAL-C 14
5.5.9 SEAL-S 14
5.5.10 SEAL-PC5 14
5.5.11 SEAL-UU 15
5.5.12 FAE-E 15
5.6 Capability exposure for enabling FF applications 15
6 Identities 15
6.1 General 15
6.2 Identities 15
6.2.1 FF user identity (FF user ID) 15
6.2.2 FF UE identity (FF UE ID) 15
6.2.3 FF group identity (FF group ID) 16
6.2.4 FF Application Specific Server Identifier (FASS ID) 16
6.2.5 FAE Server Identifier (FAE Server ID) 16
7 Procedures and information flows 17
7.0 Usage of SEAL services 17
7.0.1 Group management service 17
7.0.1.1 General 17
7.0.1.2 Information flows 17
7.0.1.3 Procedures 17
7.0.1.4 APIs 17
7.0.2 Configuration management service 17
7.0.2.1 General 17
7.0.2.2 Information flows 17
7.0.2.3 Procedures 17
7.0.2.4 APIs 17
7.0.3 Location management service 17
7.0.3.1 General 17
7.0.3.2 Information flows 17
7.0.3.3 Procedures 17
7.0.3.4 APIs 17
7.0.4 Identity management service 17
7.0.4.1 General 17
7.0.4.2 Information flows 17
7.0.4.3 Procedures 17
7.0.5 Key management service 18
7.0.5.1 General 18
7.0.5.2 Information flows 18
7.0.5.3 Procedures 18
7.0.6 Network resource management service 18
7.0.6.1 General 18
7.0.6.2 Information flows 18
7.0.6.3 Procedures 18
7.0.6.4 APIs 18
8 APIs 18
Annex A (Informative): Deployment models 19
A.1 General 19
A.2 Deployment of FAE+SEAL server 19
A.2.0 General 19
A.2.1 Centralized deployments 19
A.2.2 Distributed deployment 22
A.3 Deployment of FFAPP with Edge Enabler Layer 24
A.3.1 General 24
A.3.2 Description 24
Annex B (Informative): Involved entities and relationships 25
B.1 General 25
Annex C (Informative): Guideline for service enablers usage 26
C.0 General 26
C.1 Support for TSC services 27
C.1.1 General 27
C.1.2 TSC stream resource management 27
C.1.2.1 TSC stream availability discovery 27
C.1.2.2 TSC stream creation 27
C.1.2.3 TSC stream deletion 27
C.1.3 TSN Bridge resource management 28
C.1.3.1 TSN Bridge information reporting 28
C.1.3.2 TSN Bridge configuration 28
C.2 Support for MSGin5G services 28
C.2.1 General 28
C.2.2 Registration 29
C.2.2.1 MSGin5G UE Registration 29
C.2.2.2 MSGin5G UE De-Registration 29
C.2.2.3 Application Server Registration 29
C.2.2.4 Application Server De-registration 29
C.2.3 Message delivery procedures into and from MSGin5G Server 29
C.2.3.1 MSGin5G inbound messages into the MSGin5G Server 29
C.2.3.2 MSGin5G outbound messages from the MSGin5G Server 29
C.2.3.3 MSGin5G message delivery status report into the MSGin5G Server 30
C.2.3.4 MSGin5G message delivery status report from the MSGin5G Server 30
C.2.3.5 MSGin5G Store and Forward 30
C.2.4 Message Aggregation 30
C.2.4.1 Message Aggregation at MSGin5G Client 30
C.2.3.2 Message Aggregation at MSGin5G Server 30
C.2.5 MSGin5G Message Segmentation and Reassembly 30
C.2.5.1 Application-to-Point Segmentation and Reassembly 30
C.2.5.2 Point-to-Application Message Segmentation and Reassembly 30
C.2.5.3 Point-to-Point Message Segmentation and Reassembly 31
C.2.5.4 MSGin5G Message Segment Recovery 31
C.2.6 E2E Message delivery procedures 31
C.2.6.1 Point-to-Point Message delivery procedure 31
C.2.6.2 Application-to-Point Message delivery procedure 31
C.2.6.3 Point-to-Application Message delivery procedure 31
C.2.6.4 MSGin5G Group messaging 31
C.2.7 Message Topic 31
C.2.7.1 Messaging Topic Subscription 31
C.2.7.2 Message delivery based on Messaging Topic 31
C.2.7.3 Messaging Topic Unsubscription 32
C.2.8 Constrained devices 32
C.2.8.1 Constrained device registration to use gateway UE 32
C.2.8.2 Constrained device Deregistration from using gateway UE 32
C.2.8.3 Constrained device sending message using Gateway UE 32
C.2.8.4 Constrained device receiving message via Gateway UE 32
C.3 Support for FF message delivery by SEALDD 32
C.3.1 General 32
C.3.2 SEALDD regular connection establishment 32
C.3.3 SEALDD enabled E2E redundant transmission 33
Annex D (informative): Change history 34