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 |
||||