Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
TS-0020
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Specifications
Technical Specifications
TS-0020
Commits
af8d9671
Commit
af8d9671
authored
1 year ago
by
Miguel Angel Reina Ortega
Browse files
Options
Downloads
Patches
Plain Diff
Adding participants to mermaid diagrams
parent
4f7f5499
No related branches found
No related tags found
1 merge request
!5
SDS-2024-0021-Corrections_for_WS_binding
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
TS-0020-WebSocket_Protocol_Binding.md
+19
-12
19 additions, 12 deletions
TS-0020-WebSocket_Protocol_Binding.md
with
19 additions
and
12 deletions
TS-0020-WebSocket_Protocol_Binding.md
+
19
−
12
View file @
af8d9671
...
...
@@ -496,17 +496,24 @@ Figure A.1-1 illustrates a message flow for registration of an ADN-AE to an IN-C
```
mermaid
%%{init: { 'sequence': {'mirrorActors': false, 'actorFontSize': 2, 'noteFontSize':10} } }%%
sequenceDiagram
Note over AE, IN-CSE: 1) TCP connection and Security<br/>Association Establishment
AE ->> IN-CSE: 2) WSS client handshake
IN-CSE ->> AE: 3) WSS server handshake
AE ->> IN-CSE: 4) Create AE request primitive
Note over IN-CSE: 5) Check access controls, process request<br/>and create <AE> resource for originating AE
IN-CSE ->> AE: 6) Response primitive
AE ->> IN-CSE: 7) Create Container request primitive
Note over IN-CSE: 8) Check access controls, process request and<br/>create <Container> resource for originating AE
IN-CSE ->> AE: 9) Response primitive
Note over AE, IN-CSE: 10) Other procedures
Participant ADNAE1 as ADN-AE1
Participant ADNAE2 as ADN-AE2
Participant MNAE as MN-AE
Participant MNCSE as MN-CSE
Participant INCSE as IN-CSE
Participant INAE as IN-AE
MNAE ->> MNCSE: 1) Group resource<br />creation for updating<br />and retrieval of the state<br />of a group of lights
Note right of MNCSE: Group resource is created<br />with a specific access<br />control policy under MN-CSE
ADNAE1 ->> MNCSE: 2-1) Container resource<br />creation of light_1
ADNAE2 ->> MNCSE: 2-2) Container resource<br />creation of light_2
Note right of MNCSE: Container resources are<br />created with a specific access<br />control policy under MN-CSE
ADNAE1 ->> MNCSE: 3-1) ContentInstance<br />resource creation<br />under container of light_1
ADNAE2 ->> MNCSE: 3-2) ContentInstance<br />resource creation<br />under container of light_2
Note right of MNCSE: ContentInstance resources are<br />created under the containers<br />in MN-CSE
ADNAE1 ->> MNCSE: 4-1) Subscription resource<br />creation to container of light_1
ADNAE2 ->> MNCSE: 4-2) Subscription resource<br />creation to container of light_2
Note right of MNCSE: Subscription resources to<br />containers in MN-CSE are<br />created for monitoring<br />contentInstance updates
```
**Figure A.1-1: Message flow for registration of an ADN-AE to an IN-CSE**
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment