hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.3 AP call initiation procedure | On receipt of the call initiation request from the App, the AP shall follow normal session establishment and data exchange procedures with the App. The AP shall then construct and send an EDS to its associated PSP, following standard PEMEA procedures as stipulated in ETSI TS 103 478 [1]. ETSI ETSI TS 103 945 V1.1.1 (20... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.4 PIM emergency session establishment procedures | On receipt of an EDS containing the PAV capability, a PIM supporting the function shall immediately indicate its support to the originating AP through the onCapSupportPost procedure stipulated in ETSI TS 103 478 [1]. The PIM shall then notify the PSAP of the arrival of the EDS. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.5 AP session binding procedures | On receipt of an onCapSupportPost message for a session from a valid PIM or PSP the AP shall perform all normal procedures and data exchanges with the App over Pa including notification of PSAP support for the PAV capability. The AP shall then bind the session to the PIM that sent the onCapSupportPost message and shall... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.6 PEMEA Audio_Video invocation procedures | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.6.1 Service invocation flow | Under direction of a PSAP Call-Taker the PIM shall proceed to acquire the necessary resources to invoke the PAV capability in the AP. The PIM shall request the creation of an Audio_Video signalling room to the Audio_Video signalling server. The Audio_Video signalling room shall be identified through a unique HTTPS URI.... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.6.2 Service invocation object | The PIM invokes the PEMEA Audio_Video (PAV) service in the AP by posting to the URI provided in the Audio_Video information element included in the apMoreInformation contained in the EDS. The POST message includes a body containing a JSON object. The JSON object provides the Audio_Video signalling room URI as well as a... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.6.3 Audio_Video signalling room creation and deletion | The Audio_Video signalling room is created by the Audio_Video server under direction of the PSAP Call-Taker via the PIM as described in clause 8.6. Once the Audio_Video signalling room is created it remains active as long as the PIM maintains a context for the EDS. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.7 Re-invocation procedures | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.7.1 Overview | In the event of PSAP communication issues, the PSAP Call-Taker may initiate a re-invocation of the PAV capability. This has implications for all participants connected to the room and should only be done in error conditions. Under re-invocation instructions for the PAV capability from the PSAP Call-Taker the PIM shall:... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.7.2 Termination procedures | On request for Audio_Video signalling room termination from the PIM the Audio_Video signalling server shall: 1) Close opened websocket connections with all the participants. The close will be done sending a close code of 1 000 and a UTF-8 encoded reason indicating that the session has been terminated as described in th... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.7.3 Termination and Re-invocation sequences | Figure 3 provides the sequence diagram illustrating the flow of events between entities for the re-invocation procedure. Figure 3: PAV Termination and Re-Invocation sequence diagram 1) The PSAP Call-Taker requests the PIM to close the Audio_Video signalling room. 2) The PIM requests the Audio_Video Signalling Server to... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 9 Connection to the Audio_Video signalling room | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 9.1 Overview | The Audio_Video signalling room provides signalling configuration to the call participants. It also provides the means for participants to learn about the presence of other participants and to exchange signalling information that enables the establishment of media streams. Further, it provides the PSAP Call-Taker the a... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 9.2 Audio_Video signalling room joining procedure | The Audio_Video signalling room shall authenticate all participants that attempt to connect to the room URI. The token in the Authentication header field shall be used to authenticate participants. If a token has expired, is not valid or is missing, then the Audio_Video signalling room shall return an HTTP 401 "Unautho... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 9.3 PSAP Call-Taker joining procedure | To join the Audio_Video signalling room the PSAP Call-Taker equipment shall initiate an HTTPS connection to the room URI provided by the PIM. The HTTP Authentication header shall contain the security access token provided by the PIM and the token shall be placed in the Authentication header field in accordance with IET... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 9.4 AP joining procedure | To join the Audio_Video signalling room the AP shall initiate an HTTPS connection to the room URI provided by the PIM. The HTTP Authentication header shall contain the security access token provided by the PIM and the token shall be placed in the Authentication header field in accordance with IETF RFC 6750 [3] as descr... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 9.5 JOIN sequence flow | Figure 4: PAV JOIN Message sequence diagram 1) The PSAP Call-Taker connects to the Audio_Video signalling room passing in the authentication token in the Authorization HTTP header field in accordance with clause 6.2. The Audio_Video Signalling Service validates the token and upgrades the connection to a websocket. 2) T... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 10 List of users | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 10.1 Overview | After a participant successfully opens the connection with the Audio_Video signalling room and sends the JOIN message as described in clause 9, it shall receive a USER_LIST message from the Audio_Video signalling room. This message contains the list of users that are connected to the room. Each user represents a partic... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 10.2 Connection and disconnection of participants | The Audio_Video signalling room shall send a USER_LIST message each time a participant disconnects closing the websocket connection with the Audio_Video server and each time a participant sends a successful JOIN message to the Audio_Video signalling room. The participants shall compare the previously received USER_LIST... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 10.3 USER_LIST sequence flow | Figure 5: PAV USER_LIST Message sequence diagram 1) The Audio_Video signalling room sends to the PSAP Call-Taker a USER_LIST containing the PSAP user that was created from the previous JOIN message. 2) The Audio_Video signalling room sends to the PSAP Call-Taker a USER_LIST containing both the PSAP and the CALLER users... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 11 RTC session negotiation | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 11.1 Overview | Media streams in WebRTC are peer-to-peer, meaning that each participant in a WebRTC communication shall have a send channel that all other participants can listen on, and a listen channel for each participant so that they can hear what is being said. Communication streams will run through the TURN Server owing to firew... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 11.4 RTC_SESSION_NEGOTIATION message flow | The RTC_SESSION_NEGOTIATION message flow between 2 participants is too large, therefore it is divided in Figure 6 and Figure 7. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 28 Figure 6: PAV RTC_SESSION_NEGOTIATION Message sequence diagram part 1 ETSI ETSI TS 103 945 V1.1.1 (2023-11) 29 Figure 7: PAV RTC_SESSION_NEGOTIATION Me... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12 SDP negotiation | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.1 Overview | WebRTC uses Real-time Transport Protocol (RTP) to enable communication between participants. To negotiate the RTP communication, Session Description Protocol (SDP) as defined in IETF RFC 4566 [13] shall be exchanged. The IETF RFC 8839 [6] specifies how the SDP negotiation shall be made, and adds the ICE connectivity ch... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.2 SDP structure considerations | The SDP "offer" generated by participants should have the property "a=sendonly" when negotiating their Send-Only stream and it should have the property "a=recvonly" when negotiating the Receive-Only stream of other participants. When the Media Service generates the SDP "answer" for the Send-Only streams of the users, i... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.3 Negotiation of Send-Only stream | Once a participant has successfully joined the Audio_Video signalling room and received the RTC_SESSION_NEGOTIATION in which the user identification is himself, the participant shall establish the RTP communication channel to send his media to the Audio_Video session. The participant shall create a local peer-connectio... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.4 Negotiation of Receive-Only stream | When a participant wants to receive the Send-Only stream that other participant is sending to the Audio_Video Server it shall establish the RTP communication channel to receive the media streams of the selected participant. This process shall be done with all the participants from which the participant wants to receive... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.5 Re-Negotiation of Send-Only stream | Once a participant has made the SDP negotiation for his Send-Only channel described in clause 12.3 successfully, he is able to re-negotiate the Send-Only stream channel. This can be done if there is a problem with the streams or if the available media options change from the time at which the Send-Only stream channel w... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.6 Re-Negotiation of Receive-Only stream | When a participant makes the procedures described in clause 12.5, the Media Service shall reconnect the new Send-Only channel that the participant re-negotiated with all already negotiated Receive-Only streams that were already negotiated by other participants for the participant that made the re-negotiation. The Audio... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 12.8 RTC_SESSION_DESCRIPTION message flow | The RTC_SESSION_DESCRIPTION message flow between 2 participants is too large, therefore it is divided in Figure 8 and Figure 9. Figure 8: PAV RTC_SESSION_DESCRIPTION Message sequence diagram part 1 ETSI ETSI TS 103 945 V1.1.1 (2023-11) 36 Figure 9: PAV RTC_SESSION_DESCRIPTION Message sequence diagram part 2 1) After ha... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 13 ICE candidate exchange | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 13.1 Overview | The architecture of the PEMEA Audio_Video capability is described in clause 5 and explains that a TURN Server is needed to ensure that the stream flow between participants and the Media Service can always occur because in most of the cases participants could be behind NAT and thus not be able to establish the stream fl... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 13.2 ICE candidate structure considerations | All participants shall support ICE as defined in IETF RFC 8445 [5] and IETF RFC 8863 [15]. The implementation shall be a full ICE implementation since interoperability is the most important thing and a full ICE implementation allow interworking with both ICE and ICE-Lite implementations. All participants shall support ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 13.3 Exchange of ICE candidates | Clauses 12.3, 12.4, 12.5 and 12.6 describe how the participants shall generate a SDP offer from a local peer-connection and exchange it with the Audio_Video Server depending on what stream they want to negotiate, and how the Audio_Video Server shall create a peer-connection in the Media Server for that SDP offer, and g... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 13.4 End-of-Candidates indication | As it is defined in IETF RFC 8838 [12], an end-of-candidates indication should be sent between the RTC peers, but it does not specify how to signal this indication. When a participant and the Media Service have ended the process of generating ICE candidates for a certain peer- connection, they shall send an extra RTC_I... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 13.5 RTC_ICE_CANDIDATE message flow | The RTC_ICE_CANDIDATE message flow between 2 participants is too large, therefore it is divided in Figure 10 and Figure 11. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 40 Figure 10: PAV RTC_ICE_CANDIDATE Message sequence diagram part 1 ETSI ETSI TS 103 945 V1.1.1 (2023-11) 41 Figure 11: PAV RTC_ICE_CANDIDATE Message sequence... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 14 User media | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 14.1 Overview | The PEMEA Audio_Video (PAV) architecture is described in clause 5 and includes a Media Server to which the participants establish their Send-Only streams to send its streams to the Audio_Video Server and their Receive-Only channels to receive individually the streams that are being sent by other participants to the Aud... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 14.2 User media properties | The audio property indicates whether the audio channel of the Send-Only stream that the participant has negotiated with the Audio_Video Server is being muted locally or not. True means that the stream has useful information, false means that it is being muted locally by the participant. The video property indicates whe... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 14.3 USER_MEDIA message flow | Figure 12: PAV USER_MEDIA Message sequence diagram 1) If the PSAP Call-Taker wants to communicate some modification in its media, it shall send a USER_MEDIA message to the Audio_Video signalling room. 2) When the Audio_Video signalling room receives a USER_MEDIA message it shall broadcast it to all the opened websocket... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 15 Media control | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 15.1 Overview | PSAP's usually need to have control the media streams of other participants, this includes functions such as muting other participants or isolate other participants so that they are not able to hear a confidential conversation related to the incident resolution. This is important in certain types of communications and ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 15.2 Permissions | The tokens shall have a payload that can be read by the Audio_Video server as described in clause 6.2 with a property to indicate if the associated user has moderator permissions. Users are listed and described in USER_LIST messages described in clause 21.4, and there the moderator property indicates if the user has mo... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 15.3 Mute a participant | In order to mute a certain participant, a participant with moderator permissions shall send a MEDIA_CONTROL message with the target property set to the value of the user identification of the user that shall be muted. The action property shall be set to "MUTE" to mute the participant or to "UNMUTE" to stop muting the p... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 15.4 Isolate a participant | In order to isolate a certain participant, a participant with moderator permissions shall send a MEDIA_CONTROL message with the target property set to the value of the user identification of the user that shall be isolated. The action property shall be set to "HOLD" to isolate the participant or to "UNHOLD" to restore ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 15.5 MEDIA_CONTROL message flow | Figure 13: PAV MEDIA_CONTROL Message sequence diagram 1) If the PSAP with moderator permissions wants to control the media of other participant, it shall send a MEDIA_CONTROL message to the Audio_Video signalling room. 2) When the Audio_Video signalling room receives a MEDIA_CONTROL message it shall verify that the par... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 16 Change permissions | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 16.1 Overview | Sometimes the permissions of a user have to be changed. The CHANGE_PERMISSIONS message described in clause 21.10 can be used by moderator users to give or remove moderator permissions to other users. This may happen because the PAV capability is not restricted to be a one-to-one communication, multiple participants can... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 16.2 Permissions | The tokens shall have a payload that can be read by the Audio_Video server as described in clause 6.2 with a property to indicate if the associated user has moderator permissions. Users are listed and described in USER_LIST messages described in clause 21.4, and there the moderator property indicates if the user has mo... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 16.3 Give moderator permissions to a participant | In order to give moderator permissions to a participant of the Audio_Video signalling room, a participant with moderator permissions shall send a CHANGE_PERMISSIONS message with the moderator property set to true, and the target property set to the user identification of the target participant. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 16.4 Remove moderator permissions from a participant | In order to remove moderator permissions from a participant of the Audio_Video signalling room, a participant with moderator permissions shall send a CHANGE_PERMISSIONS message with the moderator property set to false, and the target property set to the user identification of the target participant. A participant with ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 16.5 CHANGE_PERMISSIONS message flow | Figure 14: PAV CHANGE_PERMISSIONS Message sequence diagram 1) If the PSAP with moderator permissions wants to change the permissions of a participant, it shall send a CHANGE_PERMISSIONS message to the Audio_Video signalling room. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 47 2) When the Audio_Video signalling room receives ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 17 Add participants to the call | The ability to add participants into the call is important as it brings additional expertise to the emergency situation that is able to assist in providing a successful outcome. The PEMEA Audio_Video (PAV) capability is based around WebRTC and the general architecture is provided in Figure 1. The general concept for li... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 18 Audio_Video signalling room closure | The Audio_Video signalling room can be closed though the PIM by the PSAP-CPE. The present document does not instruct when the PIM should close the Audio_Video session and this decision shall be made by decision of the PSAP-CPE. In most of the cases it can be done when the PSAP-Call-Taker considers the call to be termin... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 19 Leaving the Audio_Video session | When a participant wants to leave the PAV session, he only needs to close the websocket connection with the Audio_Video signalling room and drop all media streams. When the Audio_Video signalling room notices that a participant has left the room closing his websocket connection, it shall invalidate in the Media Server ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20 Abnormal behaviour procedures | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.1 Overview | Clause 5.2 defines the different logical components that conform the PEMEA Audio_Video (PAV) capability that are referenced in this clause. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.2 Failure of Audio_Video Signalling Server | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.2.1 Audio_Video Signalling Server failure scenarios | There are 2 main errors that can occur with the Audio_Video Signalling Server logical component, which are that the Audio_Video Signalling Server goes down unexpectedly, or that connectivity to the Audio_Video Signalling Server is lost. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.2.2 Audio_Video Signalling Server goes down | If the Audio_Video Signalling Server logical component goes down unexpectedly, the websocket connections opened to the ongoing Audio_Video sessions will be closed. The clients of websocket connections will receive the close of the websocket connection from the Audio_Video Server. When the close of the websocket connect... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.2.3 Audio_Video Signalling Server loses connectivity | If the connectivity with the Audio_Video Signalling Server is lost, it can be detected by connected websocket clients with the ping-pong mechanism described in clause 5.5 of IETF RFC 6455 [4]. If the AP, the PSAP-CPE or a third party detects with the websocket ping-pong mechanism that the websocket connection with the ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.3 Failure of Media Server | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.3.1 Media Server failure scenarios | There are 2 main errors that can occur with the Media Server logical component, which are that the Media Server fails or goes down unexpectedly, or that connectivity to the Media Server is lost. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.3.2 Media Server failure | If the Media Server logical component goes down unexpectedly, all the participants streams are dropped since the negotiations are made between peer-connections of the participants and the peer-connections of the Media Server. The Audio_Video Server shall detect the failure of the Media Server, and shall send an ERROR m... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.3.3 Media Server loses connectivity | If the connectivity loss is between the Audio_Video Signalling Server and the Media Server, the Audio_Video Signalling Server shall detect it. The detection mechanism is left to implementation. When detecting that the connectivity between the Audio_Video Signalling Server and the Media Server is lost, the Audio_Video S... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.4 Failure of TURN Server | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.4.1 TURN Server failure scenarios | There are 2 main errors that can occur with the TURN Server logical component, which are that the TURN Server fails or goes down unexpectedly, or that connectivity to the TURN Server is lost. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.4.2 TURN Server failure | If the TURN Server logical component goes down unexpectedly, all the participants streams are dropped as they are using the TURN Server to communicate with the Media Server. The Audio_Video Server shall detect the failure of the TURN Server, and shall send an ERROR message, as described in clause 21.11, with the reason... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.4.3 TURN Server loses connectivity | If the connectivity loss is between the Audio_Video Signalling Server and the TURN Server, the Audio_Video Signalling Server shall detect it. The detection mechanism is left to implementation. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 51 When detecting that the connectivity between the Audio_Video Signalling Server and the... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.5 Failure of PAV client | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.5.1 PAV client failures | PAV clients are the AP, the PSAP-CPE and third-parties added to a PAV session. There are 2 main errors that can occur with the PAV clients, which are that the PAV client goes down unexpectedly, or that connectivity to the PAV client is lost. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.5.2 PAV client goes down | If a PAV client goes down unexpectedly, the websocket connection to the Audio_Video Signalling Room is closed. The Audio_Video Signalling Server shall act as if the PAV client had closed his connection to the PAV session indicating that he is leaving the PAV session as it is described in the clause 19. Providing that t... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 20.5.3 PAV client loses connectivity | If the connectivity with a PAV client goes is lost, the Audio_Video Signalling Server can detect it with the ping-pong mechanism described in clause 5.5 of IETF RFC 6455 [4] over the websocket connection that was opened for that PAV client. The Audio_Video Signalling Server shall act as if the PAV client had closed his... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21 PEMEA Audio_Video message and type definitions | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.1 Overview | The PEMEA Audio_Video (PAV) protocol messages are defined as a series of JSON documents exchanged between the AP or PEMEA terminating node and an Audio_Video signalling room established inside the secure emergency network. The Audio_Video signalling room is established solely for communications with a single emergency ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2 Data types | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.1 MessageType | The MessageType enumerable defines the "type" of message being sent. Table 2: PEMEA Audio_Video message type values Value Description JOIN Message sent to the Audio_Video signalling room when the user wants to join the Audio_Video session. USER_LIST Message sent from the Audio_Video signalling room to all participants ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.2 User | Defines a user in the Audio_Video signalling room. It is used in the USER_LIST messages to indicate how the participants are using the media information. Table 3: User properties Property Type Description user UserId The participant information. Refer to Table 4. audio Boolean Whether the user is sending audio stream o... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.3 UserId | Defines a user identification in the Audio_Video signalling room. It is used to identify the users in the room. Table 4: UserId properties Property Type Description name String The name that the user wants to use. It could be a name "George", or a phone number "+34666554433", for example. role String The role defines t... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.4 PartialUserId | Defines a user identification in the Audio_Video signalling room. It is used when the users select their name and role using the JOIN message. It does not contain the uniqueId property because this information is in the payload associated with the token, and it is mandatory only that it can be read by the Audio_Video S... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.5 RtcConfiguration | Defines the configuration of the TURN Server to configure peer connections. Table 7: RtcConfiguration properties Property Type Description iceServers Array<RtcIc eServer> The list of elements that describe TURN Servers that shall be used to ensure connectivity with a participant. Refer to Table 9. iceTransportPolicy St... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.6 RtcIceServer | Defines a TURN Server address and credentials. Table 9: RtcIceServer properties Property Type Description urls Array<String> The list of URLs that shall be used to connect to the TURN Server. username String Optional. The username to use during the authentication process. credential String Optional. The credential to u... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.7 RtcSessionDescription | Defines the SDP negotiation between peers. Each RtcSessionDescription consists of a description type indicating which part of the offer/answer negotiation process it describes and of the SDP descriptor of the media session. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 55 Table 10: RtcSessionDescription properties Property Typ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.8 RtcIceCandidate | Defines the SDP negotiation between peers. Each RtcSessionDescription consists of a description type indicating which part of the offer/answer negotiation process it describes and of the SDP descriptor of the media session. Table 12: RtcIceCandidate properties Property Type Description candidate String Describes the In... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.2.9 Media | Defines the media to be affected by a MEDIA_CONTROL message. Table 13: Media values Value Description AUDIO Only the audio stream is affected. VIDEO Only the video stream is affected. ALL Both the audio and video streams are affected. 21.2.10 Action Defines the action that a MEDIA_CONTROL message shall have over the st... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.3 JOIN message | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.3.1 Message overview | The JOIN message is the message sent from the participants to the Audio_Video signalling room when the user wants to join the session. This may be the AP, the PSAP-CPE or another trusted user. Table 16: JOIN message properties Property Type Description type String Type of the message. The value is "JOIN". Refer to Tabl... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.3.2 Examples | { "type":"JOIN", "user":{ "name":"PSAP 1", "role":"PSAP" }, "audio":true, "video":true, "receiveAudio":true, "receiveVideo":true, "timestamp":1683893671026 } ETSI ETSI TS 103 945 V1.1.1 (2023-11) 57 |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.4 USER_LIST message | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.4.1 Message overview | The USER_LIST message is sent to all participants in the Audio_Video signalling room whenever a user enters and leaves the Audio_Video signalling room. It is considered that a user enters the room after having successfully opened the websocket connection and successfully sent a JOIN message. It is considered that a use... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.4.2 Examples | { "type":"USER_LIST", "users":[ { "user":{ "name":"+34611223344", "role":"CALLER", "uniqueId":"jgh204nq9md" }, "audio":true, "video":true, "receiveAudio":true, "receiveVideo":true, "moderator":false }, { "user":{ "name":"PSAP 1", "role":"PSAP", "uniqueId":"ljfvgtsy26540" }, "audio":true, "video":true, "receiveAudio":tr... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.5 RTC_SESSION_NEGOTIATION message | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.5.1 Message overview | The RTC_SESSION_NEGOTIATION message is sent from the Audio_Video signalling room to the participants. It is used to exchange the TURN Server address so that it is used during the ICE connectivity checks in order to reach a common point where the participants can communicate. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 58 Whe... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.5.2 Examples | { "type":"RTC_SESSION_NEGOTIATION", "configuration":{ "iceServers":[ { "credential":"NYRkaIcQ3vJAa50M7uWClHvYpqM=", "urls":[ "turn:36.181.54.52:3478?transport=udp" ], "username":"1683893970:Jorge_PSAP" } ], "iceTransportPolicy":"relay" }, "timestamp":1683893670757, "user": { "name":"PSAP 1", "role":"PSAP", "uniqueId":"... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.6 RTC_SESSION_DESCRIPTION message | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.6.1 Message overview | RTC_SESSION_DESCRIPTION messages are sent from the participants to the Audio_Video signalling room when using type "offer", and are sent in response from the Audio_Video signalling room back to the participants using type "answer". They are used to exchange the SDP from the participants to the Media Server to negotiate... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.6.2 Examples | Message sent from a participant to the Audio_Video signalling room: { "type":"RTC_SESSION_DESCRIPTION", "user":{ "name":"PSAP 1", "role":"PSAP", "uniqueId":"ljfvgtsy26540" }, "description":{ "type":"offer", "sdp":"v=0\r\no=- 3289333057432362461 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0 1\r\na=extmap-allow-... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.7 RTC_ICE_CANDIDATE message |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.