Skip to content
Snippets Groups Projects
Commit b01e1ec5 authored by Andreas Kraft's avatar Andreas Kraft Committed by Miguel Angel Reina Ortega
Browse files

Corrected media paths

parent 13512815
No related branches found
No related tags found
1 merge request!5SDS-2024-0021-Corrections_for_WS_binding
......@@ -150,7 +150,7 @@ An AE or CSE may optionally host a WebSocket server for situations when no WebSo
Figure 5.2-2 shows an example message flow for a scenario where an ADN-AE registers to its registrar MN-CSE using an unsecured TCP connection without proxy and then continues exchanging non-registration request and response primitives.
![Figure 5.2-2: Example message flow with WebSocket binding](/Users/akr/Sources/git/ts-0020/media/MessageFlowWebSocketBinding.png)
![Figure 5.2-2: Example message flow with WebSocket binding](media/MessageFlowWebSocketBinding.png)
**Figure 5.2-2: Example message flow with WebSocket binding**
......@@ -445,12 +445,13 @@ If no associated WebSocket connection between a registree and a registrar exists
- If the processed *pointOfAccess* address is a WebSocket URL with the value *ws://default* and there is an established WebSocket connection between the registree and the registrar, then the registrar will handle the request and response via the established WebSocket connection. If there is no established WebSocket connection, then this URI is skipped and the iteration of the *pointOfAccess* attribute continues.
- If the processed *pointOfAccess* address is a WebSocket URL other than the value *ws://default* then the registrar establishes a new WebSocket connection with the WebSocket server at that URL, if not already established, and, on success, handles the request and response via this WebSocket connection. After this the registrar may close the WebSocket connection.
For this WebSocket connection the registrar adds the *X-M2M-Origin* header with its own *CSE-ID* as the value.
> Note: In other words, a WebSocket URL address in the *pointOfAccess* attribute with a value of *ws://default* means that a request reachable registree can be reached via the WebSocket binding through an established WebSocket connection. If the *pointOfAccess* attribute contains a WebSocket URL address other than *ws://default* then this means that a WebSocket server is supported by the registree and it can be reached by establishing a new WebSocket connection by the registrar.
Figure 6.5-1 presents this procedure in a sequence.
![Figure 6.5-1: Sending notifications via WebSockets](/Users/akr/Sources/git/ts-0020/media/SendingNotificationsOverWebSocket.png)
![Figure 6.5-1: Sending notifications via WebSockets](media/SendingNotificationsOverWebSocket.png)
**Figure 6.5-1: Sending notifications via WebSockets**
......@@ -478,7 +479,7 @@ In special deployment scenarios, e.g. when the communicating oneM2M entities usi
## A.1 AE Registration and creation of a container child resource
Figure A.1-1 illustrates a message flow for registration of an ADN-AE to an IN-CSE as described in clause 7.3.5.2.1 of oneM2M TS-0004 <a href="#_ref_5">[5]</a> with WebSocket mapping and subsequent creation of a &lt;container> child resource.
![Figure A.1-1: Message flow for registration of an ADN-AE to an IN-CSE](/Users/akr/Sources/git/ts-0020/media/MessageFlowAERegistration.png)
![Figure A.1-1: Message flow for registration of an ADN-AE to an IN-CSE](media/MessageFlowAERegistration.png)
**Figure A.1-1: Message flow for registration of an ADN-AE to an IN-CSE**
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment