BS EN 62379-5-2:2014
$198.66
Common control interface for networked digital audio and video products – Transmission over networks. Signalling (TA4)
Published By | Publication Date | Number of Pages |
BSI | 2014 | 56 |
IEC 62379-5-2:2014(E) specifies protocols which can be used between networking equipment to enable the setting up of calls which are routed across different networking technologies. It also specifies encapsulation of digital media within those calls.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | CONTENTS |
9 | INTRODUCTION |
10 | 1 Scope 2 Normative references 3 Terms and definitions |
12 | 4 Identification 4.1 Byte order 4.2 Unit identification 4.3 Flow identifiers Figures Figure 1 – Structure of flow identifier |
13 | 4.4 Address format |
14 | 5 Message format 5.1 General Tables Table 1 – Address type codes |
15 | 5.2 Header Figure 2 – Signalling message format Figure 3 – Signalling message header Table 2 – Message class |
16 | 5.3 Variable part 5.3.1 General 5.3.2 Information element format Table 3 – Message type |
17 | 5.3.3 Order of occurrence of information elements Figure 4 – Information element header Figure 5 – Information element with a nonempty fixed part and a variable part |
18 | 5.4 Data formats 5.5 Contents of fixed and variable parts 5.5.1 FindRoute messages 5.5.2 ClearDown messages 5.5.3 AddFlow messages 5.5.4 NetworkData and EndToEndData messages |
19 | 5.5.5 AsyncSetup messages 5.5.6 Extended message types 5.6 Information element types 5.6.1 Coding of “type” field Table 4 – Information element types |
20 | 5.6.2 Called address 5.6.3 Flow descriptor Figure 6 – Fixed part of FlowDescriptor IE |
21 | 5.6.4 Data format or protocol 5.6.5 Start time 5.6.6 End time 5.6.7 Call importance 5.6.8 Service (or programme) name 5.6.9 Source name |
22 | 5.6.10 Destination name 5.6.11 Privilege level 5.6.12 Password 5.6.13 Charge for call 5.6.14 Calling address 5.6.15 Route metric |
23 | 5.6.16 Synchronous service parameters 5.6.17 Asynchronous service parameters |
24 | 5.6.18 Link-specific resource allocations 5.6.19 End-to-end delay 5.6.20 Route identifier of multicast Figure 7 – Fixed part of multicast route identifier IE |
25 | 5.6.21 Cause 5.6.22 Route and flow selection 5.6.23 Alternatives 5.6.24 Group |
26 | 5.6.25 Interim offer 5.6.26 Path MTU |
27 | 5.6.27 Number of destinations 5.6.28 Selector for an individual destination 5.6.29 User data 5.6.30 Extended IE types |
28 | 6 Protocols 6.1 General |
29 | 6.2 Establishing a route 6.2.1 Connection of flows 6.2.2 Request message |
31 | 6.2.3 Action on receiving a FindRoute request |
33 | 6.2.4 Action on receiving on a FindRoute response |
35 | 6.2.5 Passing on a FindRoute confirmation 6.2.6 Action of the responder on receiving a FindRoute confirmation 6.2.7 FindRoute completion message |
36 | 6.3 Disconnection of routes and flows 6.3.1 General 6.3.2 ClearDown request message |
37 | 6.3.3 Action on receiving a ClearDown request message 6.4 Adding new flows to an existing route 6.5 Information messages related to a route 6.5.1 General |
38 | 6.5.2 Notification of the number of destinations 6.5.3 Changing service parameters 6.5.4 Out-of-band data 6.6 Quasi-connectionless service 6.6.1 General 6.6.2 Request message |
39 | 6.6.3 Action on receiving request 7 Media formats 7.1 Identification 7.2 Packet data 7.2.1 General packet data |
40 | 7.2.2 Other packet formats 7.3 Pulse-code modulated audio 7.3.1 Rationale 7.3.2 Sequencing octet Figure 8 – Sequencing octet Figure 9 – “Short” bit string value |
41 | 7.3.3 Subframe format 7.3.4 Frame format Figure 10 – “Long” bit string value |
42 | 7.3.5 Transport 7.3.6 Signalling of format |
44 | 8 Cause codes 8.1 ITU-T standard cause codes 8.2 Other cause codes |
45 | Annex A (informative) Background |
54 | Bibliography |