emolero commited on
Commit
6ac8960
·
verified ·
1 Parent(s): aa15c16

Add files using upload-large-folder tool

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. marked/H/T-REC-H.130-198811-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg +3 -0
  2. marked/H/T-REC-H.130-198811-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg +3 -0
  3. marked/H/T-REC-H.130-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  4. marked/H/T-REC-H.130-198811-I_PDF-E/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg +3 -0
  5. marked/H/T-REC-H.221-200903-I_PDF-E/raw.md +0 -0
  6. marked/H/T-REC-H.223-200107-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg +3 -0
  7. marked/H/T-REC-H.223-200107-I_PDF-E/0db3cccd1279034258e5ad5b6fdcff01_img.jpg +3 -0
  8. marked/H/T-REC-H.223-200107-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg +3 -0
  9. marked/H/T-REC-H.223-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  10. marked/H/T-REC-H.223-200107-I_PDF-E/303fadfb9def251d1575d6221199b158_img.jpg +3 -0
  11. marked/H/T-REC-H.223-200107-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg +3 -0
  12. marked/H/T-REC-H.223-200107-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg +3 -0
  13. marked/H/T-REC-H.223-200107-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg +3 -0
  14. marked/H/T-REC-H.223-200107-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg +3 -0
  15. marked/H/T-REC-H.223-200107-I_PDF-E/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg +3 -0
  16. marked/H/T-REC-H.223-200107-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg +3 -0
  17. marked/H/T-REC-H.223-200107-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg +3 -0
  18. marked/H/T-REC-H.223-200107-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg +3 -0
  19. marked/H/T-REC-H.223-200107-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg +3 -0
  20. marked/H/T-REC-H.223-200107-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg +3 -0
  21. marked/H/T-REC-H.223-200107-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg +3 -0
  22. marked/H/T-REC-H.223-200107-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg +3 -0
  23. marked/H/T-REC-H.223-200107-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg +3 -0
  24. marked/H/T-REC-H.223-200107-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg +3 -0
  25. marked/H/T-REC-H.223-200107-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg +3 -0
  26. marked/H/T-REC-H.223-200107-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg +3 -0
  27. marked/H/T-REC-H.223-200107-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg +3 -0
  28. marked/H/T-REC-H.224-200501-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg +3 -0
  29. marked/H/T-REC-H.224-200501-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +3 -0
  30. marked/H/T-REC-H.224-200501-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg +3 -0
  31. marked/H/T-REC-H.224-200501-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg +3 -0
  32. marked/H/T-REC-H.224-200501-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg +3 -0
  33. marked/H/T-REC-H.224-200501-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg +3 -0
  34. marked/H/T-REC-H.224-200501-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg +3 -0
  35. marked/H/T-REC-H.226-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  36. marked/H/T-REC-H.226-199809-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg +3 -0
  37. marked/H/T-REC-H.226-199809-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg +3 -0
  38. marked/H/T-REC-H.226-199809-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg +3 -0
  39. marked/H/T-REC-H.226-199809-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg +3 -0
  40. marked/H/T-REC-H.226-199809-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg +3 -0
  41. marked/H/T-REC-H.226-199809-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +3 -0
  42. marked/H/T-REC-H.226-199809-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg +3 -0
  43. marked/H/T-REC-H.230-201905-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg +3 -0
  44. marked/H/T-REC-H.231-199707-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  45. marked/H/T-REC-H.231-199707-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg +3 -0
  46. marked/H/T-REC-H.231-199707-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg +3 -0
  47. marked/H/T-REC-H.231-199707-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg +3 -0
  48. marked/H/T-REC-H.231-199707-I_PDF-E/raw.md +552 -0
  49. marked/H/T-REC-H.233-200211-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg +3 -0
  50. marked/H/T-REC-H.233-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
marked/H/T-REC-H.130-198811-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg ADDED

Git LFS Details

  • SHA256: 95aedfb871b5bb18a71481cc390109554af647594e176731d4e480a6aeb09195
  • Pointer size: 131 Bytes
  • Size of remote file: 159 kB
marked/H/T-REC-H.130-198811-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg ADDED

Git LFS Details

  • SHA256: 6675eeab1a0fbfdaa451b118d5e1ada95b5379da3f29778479b0bf2455513e43
  • Pointer size: 131 Bytes
  • Size of remote file: 164 kB
marked/H/T-REC-H.130-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
  • Pointer size: 129 Bytes
  • Size of remote file: 7.39 kB
marked/H/T-REC-H.130-198811-I_PDF-E/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg ADDED

Git LFS Details

  • SHA256: 11140115513b142ab36e15069646b5325f25b3f1465049e6abc8a7affe058812
  • Pointer size: 130 Bytes
  • Size of remote file: 11.5 kB
marked/H/T-REC-H.221-200903-I_PDF-E/raw.md ADDED
The diff for this file is too large to render. See raw diff
 
marked/H/T-REC-H.223-200107-I_PDF-E/0c80c383f76034e117adf5e5eaadaaf3_img.jpg ADDED

Git LFS Details

  • SHA256: b24cf62713f7d725533524a500cec7371d7fee6d2559b45368ea4a5468c70b3f
  • Pointer size: 130 Bytes
  • Size of remote file: 43.9 kB
marked/H/T-REC-H.223-200107-I_PDF-E/0db3cccd1279034258e5ad5b6fdcff01_img.jpg ADDED

Git LFS Details

  • SHA256: 15cc5f52b38e35fa91c018af1667468e2293a923f4009ea837f3d368f0c8a747
  • Pointer size: 130 Bytes
  • Size of remote file: 34.3 kB
marked/H/T-REC-H.223-200107-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg ADDED

Git LFS Details

  • SHA256: 8f6cdf0e4b9f4272450643cc919f6bdbe555f387cefd93d16026bce4edabda0f
  • Pointer size: 131 Bytes
  • Size of remote file: 126 kB
marked/H/T-REC-H.223-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: ea4542563ddea0559d577b46cf697de71f819c7c39290a9dd329a27b275e025d
  • Pointer size: 129 Bytes
  • Size of remote file: 8.22 kB
marked/H/T-REC-H.223-200107-I_PDF-E/303fadfb9def251d1575d6221199b158_img.jpg ADDED

Git LFS Details

  • SHA256: 5b89bb57707edd1621a49cd6f0e6d4b8ab86de6ae0b2c8a30f634a08eaa2a8e1
  • Pointer size: 129 Bytes
  • Size of remote file: 9.74 kB
marked/H/T-REC-H.223-200107-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg ADDED

Git LFS Details

  • SHA256: 02a022b76b50d967d24df14ae6485d08653d37a66a4f3a802e5e500b9ab60436
  • Pointer size: 130 Bytes
  • Size of remote file: 25.5 kB
marked/H/T-REC-H.223-200107-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg ADDED

Git LFS Details

  • SHA256: 82a56f761907c439ff053cab2ddc073a2d9b01b010825d4527bfe3d22a545d46
  • Pointer size: 130 Bytes
  • Size of remote file: 41.9 kB
marked/H/T-REC-H.223-200107-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg ADDED

Git LFS Details

  • SHA256: 1c20c203dc2b82d91ce1f78474efdbd3a1c1b4789944d9f9d7f6d09f11c98b5e
  • Pointer size: 130 Bytes
  • Size of remote file: 14.1 kB
marked/H/T-REC-H.223-200107-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg ADDED

Git LFS Details

  • SHA256: cbc80de58f437d0c6e755c9407eafc27a3659696fe5599a1603f5f00bf301016
  • Pointer size: 130 Bytes
  • Size of remote file: 93.9 kB
marked/H/T-REC-H.223-200107-I_PDF-E/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg ADDED

Git LFS Details

  • SHA256: 9113b30d32e3928ef7531c9b5b00e758c36b8499be195201c10a30da3ba7cd16
  • Pointer size: 130 Bytes
  • Size of remote file: 21.9 kB
marked/H/T-REC-H.223-200107-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg ADDED

Git LFS Details

  • SHA256: 5433fbfa3b1ee67893591eb9eef465f6eb83e4b33097b90864725362052add02
  • Pointer size: 130 Bytes
  • Size of remote file: 23.5 kB
marked/H/T-REC-H.223-200107-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg ADDED

Git LFS Details

  • SHA256: 8360edd26391ffcacc87811f1a8938ff8fd07d2b61d29468f96c92e18ea49042
  • Pointer size: 130 Bytes
  • Size of remote file: 22 kB
marked/H/T-REC-H.223-200107-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg ADDED

Git LFS Details

  • SHA256: 48aed3ff9bc5604389412a0626b613c8c801941337798c4918f67a9ccadb9c08
  • Pointer size: 130 Bytes
  • Size of remote file: 75.3 kB
marked/H/T-REC-H.223-200107-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg ADDED

Git LFS Details

  • SHA256: 4899846c8757487b0612398f89f64ed9a42d39e7eb6d11f534a78ecda3dcb7a2
  • Pointer size: 130 Bytes
  • Size of remote file: 53.8 kB
marked/H/T-REC-H.223-200107-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg ADDED

Git LFS Details

  • SHA256: 2f33c677501fef50595f29105c6574f2988181c8c286cc2ce8edd163dcb832b8
  • Pointer size: 130 Bytes
  • Size of remote file: 26.1 kB
marked/H/T-REC-H.223-200107-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg ADDED

Git LFS Details

  • SHA256: 9a7216b892160e79f4989893054185f72f2df3b44b9fe08105fb6c0aa0a951e5
  • Pointer size: 130 Bytes
  • Size of remote file: 23.6 kB
marked/H/T-REC-H.223-200107-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg ADDED

Git LFS Details

  • SHA256: 6bf2a24a84a13455736994a908f15f3ed85e3831740e68de562e80849d9f1840
  • Pointer size: 129 Bytes
  • Size of remote file: 8.14 kB
marked/H/T-REC-H.223-200107-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg ADDED

Git LFS Details

  • SHA256: a41d91272bf49ba292ee617d66d4314d31737384164b5aa37c0e68747d8ac256
  • Pointer size: 130 Bytes
  • Size of remote file: 25.5 kB
marked/H/T-REC-H.223-200107-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg ADDED

Git LFS Details

  • SHA256: 1055226f8e1638e05f7e67f3a2c96ddb01052b88ba23168fe4d39034cedcc7a4
  • Pointer size: 130 Bytes
  • Size of remote file: 44.4 kB
marked/H/T-REC-H.223-200107-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg ADDED

Git LFS Details

  • SHA256: f50342aa7490b8bbb88112ff3ea6db88fbedb3bcae038b310b00ac66043d01ad
  • Pointer size: 130 Bytes
  • Size of remote file: 24.6 kB
marked/H/T-REC-H.223-200107-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg ADDED

Git LFS Details

  • SHA256: cb11ec0864f1dfa1afc813714710859737c34a987184f504853b4027ca56741d
  • Pointer size: 131 Bytes
  • Size of remote file: 237 kB
marked/H/T-REC-H.223-200107-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg ADDED

Git LFS Details

  • SHA256: 17202313dc5e864787fc5ab246c6128262bd8b91b81cf09443c02de821cb723c
  • Pointer size: 130 Bytes
  • Size of remote file: 53.4 kB
marked/H/T-REC-H.224-200501-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg ADDED

Git LFS Details

  • SHA256: 97a2f984f9c773986624464fe72f65f962b38b8fe1576d3396077e47ed00096a
  • Pointer size: 130 Bytes
  • Size of remote file: 69.2 kB
marked/H/T-REC-H.224-200501-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg ADDED

Git LFS Details

  • SHA256: b4575e2545123ee71a51cc7e2fc61bfe0cf1a3f72e6dfa51826374a9c1935125
  • Pointer size: 131 Bytes
  • Size of remote file: 119 kB
marked/H/T-REC-H.224-200501-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg ADDED

Git LFS Details

  • SHA256: 5c7ea13a1c56f40e666e5713af847a65408f887b94204247712dd2d7c27a0104
  • Pointer size: 130 Bytes
  • Size of remote file: 59.5 kB
marked/H/T-REC-H.224-200501-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg ADDED

Git LFS Details

  • SHA256: bd413a0aeb6d147469347f7e6eefd30d233a9163db9f233f65975bb4e8a027a8
  • Pointer size: 130 Bytes
  • Size of remote file: 47.2 kB
marked/H/T-REC-H.224-200501-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg ADDED

Git LFS Details

  • SHA256: 5928e4f7771c443814240cb3037fba121c43d8162001dbff6a0077b4522d442d
  • Pointer size: 130 Bytes
  • Size of remote file: 42.5 kB
marked/H/T-REC-H.224-200501-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg ADDED

Git LFS Details

  • SHA256: 11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3
  • Pointer size: 129 Bytes
  • Size of remote file: 4.34 kB
marked/H/T-REC-H.224-200501-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg ADDED

Git LFS Details

  • SHA256: 9c4f2989b82ad96c33b96a2058e3c10177e6de929a169951a8d93ae773c41a8e
  • Pointer size: 130 Bytes
  • Size of remote file: 12.5 kB
marked/H/T-REC-H.226-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae
  • Pointer size: 129 Bytes
  • Size of remote file: 8.2 kB
marked/H/T-REC-H.226-199809-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg ADDED

Git LFS Details

  • SHA256: 6e0e2f25b6764711dad4c12fe935e509f6f5bddb62ce78e81ae615c18f71d3bc
  • Pointer size: 130 Bytes
  • Size of remote file: 62.1 kB
marked/H/T-REC-H.226-199809-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg ADDED

Git LFS Details

  • SHA256: 663964f67d670d695619bd406b90bb355398827db9c0c2301748c0f9cc81d6dc
  • Pointer size: 130 Bytes
  • Size of remote file: 65.4 kB
marked/H/T-REC-H.226-199809-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg ADDED

Git LFS Details

  • SHA256: ebc02150fe2b8ca72b5f7934c3d7e603ae6a0bfbf8000aa3f2685e00352881e4
  • Pointer size: 130 Bytes
  • Size of remote file: 19.5 kB
marked/H/T-REC-H.226-199809-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg ADDED

Git LFS Details

  • SHA256: 743f31ee950b4a7252de347ddbc1530669d3549f83d9d794660e0a4ba9c70874
  • Pointer size: 129 Bytes
  • Size of remote file: 5.52 kB
marked/H/T-REC-H.226-199809-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg ADDED

Git LFS Details

  • SHA256: 6aac3e1aaa57ebb8ad8d2bc43b7ba918bf5fbd71b89c8008ff243ba28e2857c2
  • Pointer size: 130 Bytes
  • Size of remote file: 65.4 kB
marked/H/T-REC-H.226-199809-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg ADDED

Git LFS Details

  • SHA256: 712d82264120d98143bf28cd0ca2942df109e599ac9374ebb1ef0c1a320bf7cb
  • Pointer size: 130 Bytes
  • Size of remote file: 61.1 kB
marked/H/T-REC-H.226-199809-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg ADDED

Git LFS Details

  • SHA256: c30511dd22070bf82b3a7cd38a7878d4324c9dfb6a920e74b11db98eff998a34
  • Pointer size: 130 Bytes
  • Size of remote file: 59.5 kB
marked/H/T-REC-H.230-201905-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg ADDED

Git LFS Details

  • SHA256: aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055
  • Pointer size: 129 Bytes
  • Size of remote file: 6.86 kB
marked/H/T-REC-H.231-199707-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: c658328e03821bf4d10ed875941f8b0c2987a826db877759e1bce07c8696fd2b
  • Pointer size: 129 Bytes
  • Size of remote file: 8.27 kB
marked/H/T-REC-H.231-199707-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg ADDED

Git LFS Details

  • SHA256: 78ac6ceb861f0efdd09c38422bf74fab153cc7548e4b16890c19e0460d5a9a7c
  • Pointer size: 130 Bytes
  • Size of remote file: 51.6 kB
marked/H/T-REC-H.231-199707-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg ADDED

Git LFS Details

  • SHA256: 2673414715f900cb713cbc8827c566586a3d1ac048459ed267f8daab0dee88c2
  • Pointer size: 130 Bytes
  • Size of remote file: 87.4 kB
marked/H/T-REC-H.231-199707-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg ADDED

Git LFS Details

  • SHA256: 4e96f817810094fc8f47fd62e0391ddb6054ee9a89d7b28be71f09c425b4d380
  • Pointer size: 130 Bytes
  • Size of remote file: 18.5 kB
marked/H/T-REC-H.231-199707-I_PDF-E/raw.md ADDED
@@ -0,0 +1,552 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ TELECOMMUNICATION
14
+ STANDARDIZATION SECTOR
15
+ OF ITU
16
+
17
+ **H.231**
18
+
19
+ (07/97)
20
+
21
+ SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
22
+ Infrastructure of audiovisual services – Systems aspects
23
+
24
+ ---
25
+
26
+ **Multipoint control units for audiovisual systems
27
+ using digital channels up to 1920 kbit/s**
28
+
29
+ ITU-T Recommendation H.231
30
+
31
+ (Previously CCITT Recommendation)
32
+
33
+ ---
34
+
35
+ # ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS**
36
+
37
+ | | |
38
+ |------------------------------------------------------------------------------------------------------------|--------------------|
39
+ | Characteristics of transmission channels used for other than telephone purposes | H.10–H.19 |
40
+ | Use of telephone-type circuits for voice-frequency telegraphy | H.20–H.29 |
41
+ | Telephone circuits or cables used for various types of telegraph transmission or simultaneous transmission | H.30–H.39 |
42
+ | Telephone-type circuits used for facsimile telegraphy | H.40–H.49 |
43
+ | Characteristics of data signals | H.50–H.99 |
44
+ | CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS | H.100–H.199 |
45
+ | INFRASTRUCTURE OF AUDIOVISUAL SERVICES | H.200–H.399 |
46
+ | General | H.200–H.219 |
47
+ | Transmission multiplexing and synchronization | H.220–H.229 |
48
+ | <b>Systems aspects</b> | <b>H.230–H.239</b> |
49
+ | Communication procedures | H.240–H.259 |
50
+ | Coding of moving video | H.260–H.279 |
51
+ | Related systems aspects | H.280–H.299 |
52
+ | Systems and terminal equipment for audiovisual services | H.300–H.399 |
53
+
54
+ *For further details, please refer to ITU-T List of Recommendations.*
55
+
56
+ # **ITU-T RECOMMENDATION H.231**
57
+
58
+ # **MULTIPOINT CONTROL UNITS FOR AUDIOVISUAL SYSTEMS USING DIGITAL CHANNELS UP TO 1920 kbit/s**
59
+
60
+ ## **Summary**
61
+
62
+ This Recommendation specifies the means by which three or more audiovisual terminals conforming to Recommendation H.320 may communicate simultaneously over constant bit rate digital paths, such communication being designated a "multipoint call".
63
+
64
+ ## **Source**
65
+
66
+ ITU-T Recommendation H.231 was revised by ITU-T Study Group 16 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 10th of July 1997.
67
+
68
+ ## FOREWORD
69
+
70
+ ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
71
+
72
+ The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
73
+
74
+ The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
75
+
76
+ In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
77
+
78
+ ## NOTE
79
+
80
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
81
+
82
+ ## INTELLECTUAL PROPERTY RIGHTS
83
+
84
+ The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
85
+
86
+ As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
87
+
88
+ © ITU 1998
89
+
90
+ All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
91
+
92
+ ## CONTENTS
93
+
94
+ *Page*
95
+
96
+ | | | |
97
+ |-----|-----------------------------------------------------------------|----|
98
+ | 1 | Scope..... | 1 |
99
+ | 2 | References..... | 1 |
100
+ | 3 | Definitions..... | 2 |
101
+ | 4 | Abbreviations..... | 3 |
102
+ | 5 | Functional representation..... | 4 |
103
+ | 5.1 | General representation..... | 4 |
104
+ | 5.2 | Description of functional units..... | 4 |
105
+ | 6 | Multipoint configurations..... | 8 |
106
+ | 7 | Multipoint control unit characteristics and classification..... | 8 |
107
+ | 7.1 | Conformance..... | 8 |
108
+ | 7.2 | Classification of MCUs..... | 9 |
109
+ | 7.3 | Summary of MCU BAS capabilities..... | 9 |
110
+ | 7.4 | Other attributes..... | 10 |
111
+ | 8 | "Listed" multipoint control units..... | 10 |
112
+ | 9 | Terminal requirements and options..... | 11 |
113
+
114
+
115
+
116
+ # MULTIPOINT CONTROL UNITS FOR AUDIOVISUAL SYSTEMS USING DIGITAL CHANNELS UP TO 1920 kbit/s
117
+
118
+ (revised in 1997)
119
+
120
+ ## 1 Scope
121
+
122
+ This Recommendation specifies the means by which three or more audiovisual terminals conforming to Recommendations H.320, H.221, H.242, H.261, H.262 and H.263 may communicate simultaneously over constant bit rate digital paths, such communication being designated a "multipoint call". The terminals should not need any modification for multipoint working, though some optional enhancements may require additional software; in particular, considerably enhanced functionality is attained via the use of T.120 protocols in the MLP channel. The interconnection is effected by one or more Multipoint Control Units (MCU) which may reside in the network or at one of the terminals.
123
+
124
+ This Recommendation covers both mandatory requirements and optional enhancements for multipoint working. The optional enhancements include:
125
+
126
+ - numbering of terminals;
127
+ - chair control;
128
+ - data broadcast;
129
+ - video mixing;
130
+ - cascading.
131
+
132
+ ## 2 References
133
+
134
+ The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
135
+
136
+ - CCITT Recommendation G.711 (1988), *Pulse Code Modulation (PCM) of voice frequencies*.
137
+ - CCITT Recommendation G.722 (1988), *7 kHz Audio-coding within 64 kbit/s*.
138
+ - CCITT Recommendation G.728 (1992), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction*.
139
+ - ITU-T Recommendation H.221 (1997), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices*.
140
+ - ITU-T Recommendation H.230 (1997), *Frame synchronous control and indication signals for audiovisual systems*.
141
+ - ITU-T Recommendation H.233 (1995), *Confidentiality system for audiovisual services*.
142
+ - ITU-T Recommendation H.234 (1994), *Encryption key management and authentication system for audiovisual services*.
143
+ - ITU-T Recommendation H.242 (1997), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s*.
144
+ - ITU-T Recommendation H.243 (1997), *Procedures for establishing communication between three or more audiovisual terminals using digital channels up to 1920 kbit/s*.
145
+
146
+ - ITU-T Recommendation H.320 (1997), *Narrow-band visual telephone systems and terminal equipment*.
147
+ - ITU-T Recommendation T.122 (1993), *Multipoint communication service for audiographics and audiovisual conferencing service definition*.
148
+ - ITU-T Recommendation T.123 (1996), *Network specific data protocol stacks for multimedia conferencing Teleconference Applications*.
149
+ - ITU-T Recommendation T.124 (1995), *Generic conference control*.
150
+ - ITU-T Recommendation T.125 (1994), *Multipoint communication service protocol specification*.
151
+ - ITU-T Recommendation H.224 (1995), *A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels*.
152
+ - ITU-T Recommendation H.261 (1993), *Video codec for audiovisual systems at $p \times 64$ kbit/s*.
153
+ - ITU-T Recommendation H.262 (1995), *Generic coding of moving pictures and associated audio information: Video*.
154
+ - ITU-T Recommendation H.263 (1996), *Video coding for low bit rate communication*.
155
+
156
+ # 3 Definitions
157
+
158
+ This Recommendation defines the following terms:
159
+
160
+ **3.1 adding and dropping terminals from a conference:** Refers to connection to the APU, VPU and DPU (see 5.2), not to network (dis-)connection which is outside the scope of this Recommendation.
161
+
162
+ **3.2 chair-control terminal:** An enhanced terminal possessing a token conveying a certain measure of authority over the operation of the MCU; the token may be assigned by rearrangement, by an operator, or by protocol during the call. The person controlling need not be the actual chairperson of the meeting.
163
+
164
+ **3.3 chair-control port:** That port of the MCU serving the terminal to which chair-control has been assigned (this port is not physically different from the others).
165
+
166
+ **3.4 directly-connected terminal:** Where reference is made to "directly" connected terminals, this should not be taken to mean that the terminal in question is collocated with the MCU, but rather that it is not connected to a different MCU.
167
+
168
+ **3.5 local MCU:** That to which the terminal in question is directly connected.
169
+
170
+ **3.6 multipoint control unit (MCU):** A multi-port device, by means of which two or more audiovisual terminals may intercommunicate in a conference call; a "listed MCU" has the properties defined in clause 8. Master and Slave MCUs: A "master MCU" has been assigned a superior controlling function in a call where two or more MCUs are interconnected, while the other MCUs in that call are termed "slave MCUs".
171
+
172
+ NOTE – The physical realization of an MCU may be such that two or more independent conferences may be set up within the same unit; logically, however, there is no relationship between these conferences; the text herein refers to an MCU only as a logical entity pertinent to the particular call of concern.
173
+
174
+ **3.7 primary and secondary ports:** While all ports of an MCU may be physically the same, distinctions may be made by the internal software, on the basis of declared terminal capabilities, such that the ports are not all treated on an equal basis. In general, a multipoint call will involve two or more terminals intercommunicating on an equal basis, at their highest common capability; the MCU would designate as "primary" those ports to which these terminals are connected, and for simplicity these terminals can be referred to as "primary terminals" for the purposes of this one call. The selection of an appropriate common level for primary communication is described in Recommendation H.243.
175
+
176
+ One or more additional terminals may take part in the multipoint call, even though they do not have sufficient capability to communicate on an equal basis with primary terminals; these may be designated "secondary terminals", communicating with the others only by such compatible signals as can be made available (e.g. speech only), the MCU having designated the appropriate port accordingly. Note that if this provision were not made, then the addition of a telephony terminal to a videophone conference would cause all picture transmission to be discontinued.
177
+
178
+ It is not mandatory that an MCU be able to handle secondary terminals; in such a case, the MCU may either:
179
+
180
+ - a) disconnect a terminal not declaring capabilities adequate to participate as a primary; or
181
+ - b) lower its definition of "primary" to include the said terminal.
182
+
183
+ The provider of the MCU should make clear which procedure is followed.
184
+
185
+ ## 4 Abbreviations
186
+
187
+ This Recommendation uses the following abbreviations:
188
+
189
+ | | |
190
+ |---------|-------------------------------------------------------|
191
+ | APU | Audio Processing Unit |
192
+ | BAS | Bit-rate Allocation Signal |
193
+ | CIF | Common Intermediate Format |
194
+ | CPU | Control Processing Unit |
195
+ | DPU | Data Processing Unit |
196
+ | ECS | Encryption Control Signal |
197
+ | FAS | Frame Alignment Signal |
198
+ | FAW | Frame Alignment Word |
199
+ | GOB | Group of Blocks |
200
+ | H-MLP | High speed Multi-Layer Protocol |
201
+ | HSD | High Speed Data |
202
+ | LD-CELP | Low Delay – Code Excited Linear Prediction |
203
+ | LSB | Least Significant Bit |
204
+ | LSD | Low Speed Data |
205
+ | MB | H.261/H.262/H.263 Macroblock |
206
+ | MBE | Multi-Byte Extension |
207
+ | MCC | Multipoint Command Conference |
208
+ | MCN | Multipoint Command Negating |
209
+ | MCS | Multipoint Command Data Symmetrical Data-Transmission |
210
+ | MF | MultiFrame |
211
+ | MLP | Multi-Layer Protocol |
212
+ | MPI | Minimum Picture Interval |
213
+ | MSB | Most Significant Bit |
214
+ | NS | Non-Standard |
215
+ | PCM | Pulse Code Modulation |
216
+ | QCIF | Quarter Common Intermediate Format |
217
+ | SBE | Single Byte Extension |
218
+ | SC | Service Channel |
219
+ | SCM | Selected Communications Mode |
220
+ | SMF | Sub-MultiFrame |
221
+ | SP | Still Picture |
222
+ | VCF | Video Command "Freeze Picture Request" |
223
+ | VCU | Video Command "Fast Update Request" |
224
+ | VPU | Video Processing Unit |
225
+
226
+ # 5 Functional representation
227
+
228
+ ## 5.1 General representation
229
+
230
+ A multipoint call may be represented as in Figure 1, wherein are shown a number of terminals $T$ , not necessarily identical, linked individually into a network by symmetrical bidirectional digital connections, not necessarily all of the same capacity. There is no particular limit set by the system to the number $N$ of terminals connected in the call, though in practice, depending on implementation, the difficulties and cost will rise as $N$ increases, while performance tends to fall.
231
+
232
+ ![Diagram of a multipoint call representation showing a central network cloud connected to multiple terminals T1, T2, T3, T4, and Tn.](e6df2733626a85205c1db682e6259c46_img.jpg)
233
+
234
+ ```
235
+
236
+ graph LR
237
+ T1((T1)) --- Network
238
+ T2((T2)) --- Network
239
+ T3((T3)) --- Network
240
+ T4((T4)) --- Network
241
+ Tn((Tn)) --- Network
242
+ subgraph NetworkCloud [Network]
243
+ Network
244
+ end
245
+
246
+ ```
247
+
248
+ The diagram illustrates a central cloud-like shape labeled "Network". Surrounding this cloud are five circular nodes representing terminals: $T_1$ (top left), $T_2$ (bottom left), $T_3$ (bottom right), $T_4$ (middle right), and $T_n$ (top center). Each terminal is connected to the network cloud by a single line. A series of three dots between $T_n$ and $T_4$ indicates additional possible terminals. The reference code "T1518800-95/d01" is printed at the bottom right of the diagram area.
249
+
250
+ Diagram of a multipoint call representation showing a central network cloud connected to multiple terminals T1, T2, T3, T4, and Tn.
251
+
252
+ **Figure 1/H.231 – Representation of a multipoint call**
253
+
254
+ In the representation of Figure 1, the network need only be described by the signal flows at its ports, and their interdependencies. The hardware realization need not be of concern: there may be a single MCU at one location; alternatively the functions may be distributed to two or more locations, but in practical terms we then refer to a series of single MCUs linked together. In this Recommendation, the text applies in general to both single-location and distributed MCUs, and the linking of MCUs is only treated specifically where there is a particular need to do so.
255
+
256
+ The MCU is represented in more detail in Figure 2.
257
+
258
+ Each port of the MCU has a network interface unit, with associated call control if appropriate; on the MCU side of the network interface unit, the signal flows are contained in one or more bidirectional channels normally of equal capacity, according to the transfer rates listed in Annex A/H.221. The incoming flow is passed to the demultiplexer, which extracts the several types of information (audio, video, data, and control) and passes them to their respective processors. The processors are controlled in such a way that an appropriate output from each is made available for transmission to every terminal; the latter are brought together in the multiplexer to be combined into the outgoing channels.
259
+
260
+ The "call-control" and "call-control processor" units are outside the scope of this Recommendation (see Recommendation H.200/AV.440); the other units are described in the following subclauses.
261
+
262
+ ## 5.2 Description of functional units
263
+
264
+ ### 5.2.1 Network interface unit
265
+
266
+ A physical entity that converts to/from line code the signals of $64\text{ kbit/s}$ ( $56\text{ kbit/s}$ ) or multiples thereof which enter the demultiplexer and leave the multiplexer. Although in Figure 2 such a unit is shown for each multiplexer/demultiplexer pair, in practice a network interface might support a number of logical ports (see below).
267
+
268
+ ![Schematic of a multipoint control unit (Figure 2/H.231). The diagram shows a repeating structure of 'n' units. Each unit consists of a Network interface, a Demultiplexer, a Multiplexer, and a call control block. The Network interface is connected to the Demultiplexer and Multiplexer. The call control block is connected to the Multiplexer and a Call control processor. The Call control processor is connected to the Multiplexer. The Demultiplexer outputs are connected to the Audio Processing Unit, Video Processing Unit, Data Processing Unit, and Control Processing Unit. The Audio Processing Unit, Video Processing Unit, Data Processing Unit, and Control Processing Unit are connected to a common bus. The Data Processing Unit is divided into 'broadcast' and 'MLP' sections. The text 'T1518810-95/d02' is at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
269
+
270
+ T1518810-95/d02
271
+
272
+ Schematic of a multipoint control unit (Figure 2/H.231). The diagram shows a repeating structure of 'n' units. Each unit consists of a Network interface, a Demultiplexer, a Multiplexer, and a call control block. The Network interface is connected to the Demultiplexer and Multiplexer. The call control block is connected to the Multiplexer and a Call control processor. The Call control processor is connected to the Multiplexer. The Demultiplexer outputs are connected to the Audio Processing Unit, Video Processing Unit, Data Processing Unit, and Control Processing Unit. The Audio Processing Unit, Video Processing Unit, Data Processing Unit, and Control Processing Unit are connected to a common bus. The Data Processing Unit is divided into 'broadcast' and 'MLP' sections. The text 'T1518810-95/d02' is at the bottom right.
273
+
274
+ **Figure 2/H.231 – Schematic of a multipoint control unit**
275
+
276
+ ### 5.2.2 Port
277
+
278
+ A port is a logical entity which may support one audio or audiovisual terminal; it is associated with a single multiplexer and demultiplexer.
279
+
280
+ ### 5.2.3 Demultiplexer
281
+
282
+ The signal entering the demultiplexer is that transmitted by a terminal fully conforming to Recommendation H.221, so the operation is analogous to that of the receiving side of a terminal, namely:
283
+
284
+ - recovery of frame and multiframe alignment;
285
+ - buffering, synchronization and ordering of multiple channels if relevant;
286
+ - extraction of BAS codes and forwarding some of them to the control processor;
287
+ - extraction of encryption vectors and decryption if relevant;
288
+ - extraction of audio and forwarding to the audio processor;
289
+ - extraction of video and forwarding to the video processor;
290
+ - extraction of data and forwarding to the data processor.
291
+
292
+ Correct timing relationships must be maintained between mode-control BAS and the related audio, video and data.
293
+
294
+ ### 5.2.4 Audio Processing Unit (APU)
295
+
296
+ The audio processor prepares N audio outputs $r_j$ from N audio inputs $s_i$ , by switching, mixing, or a combination of these. Mixing requires the addition of linear signals $S_i$ obtained by decoding $s_i$ to linear (PCM or analog), and the recoding of the responses $R_j$ to appropriate transmission formats $r_j$ .
297
+
298
+ An audio-mixing MCU generally results in sending to each terminal the sum of the signals from all other terminals. However, as the number of audio signals involved in the summation increases, there can be an accumulation of unwanted signals (e.g. acoustic returns and noise) which eventually result in unacceptable degradation of the service to the user if additional precautions are not taken. The methods of dealing with these problems are for further study.
299
+
300
+ Some MCUs may allow terminals to be removed from the mixing function and interconnected separately, for private consultation.
301
+
302
+ If in either of the above cases the number N is limited to one, the MCU becomes audio-switching instead of audio-mixing. The audio unit may also contain a voice synthesizer or recorded message store, able to be connected into the mixing unit or separately to any terminal.
303
+
304
+ If the video signal is switched while the audio is mixed, the audio may be delayed relative to the video: to remedy this, the video should be buffered to reduce this delay to less than 30 ms.
305
+
306
+ NOTE – All MCUs shall, in conformance with 5.1/H.242, be able to receive PCM audio.
307
+
308
+ If the video signal is mixed as well as the audio signal, the video may be delayed relative to the audio signal. To remedy this, the MCU should buffer the audio to reduce this delay to less than 30 ms.
309
+
310
+ ### 5.2.5 Video Processing Unit (VPU)
311
+
312
+ The video processor can operate in ways entirely analogous to those described above for the audio processor: to each terminal may be transmitted a single video signal from another terminal, selected at a video switch; or a "mix" of some or all of the other video signals may be transmitted. In this case "mixing" takes the form of spatially multiplexing the images into a single composite image in one of many possible formats described in Recommendation H.243. Since the video mixing function is a complex process, the alternative of video switching may be preferred. As for audio switching, the choice of video may be automatic, such that the current speaker (largest value of $s_i$ ) receives the picture of the previous speaker, while all other terminals receive the picture of the current speaker; a time delay is incorporated into the switching (typical value 2 s) to avoid excessively frequent image changes, caused by spurious sounds such as coughing, knocking a microphone, and so on.
313
+
314
+ The video switching may also be controlled directly by the chairperson, if any, who makes the decision as to which picture is most appropriate. The symbol MCV (see Recommendation H.230) may be sent from a terminal to force an MCU to broadcast its video signal, overriding the automatic mechanism until "cancel-MCV" is sent; the T.120-Series Recommendations provide for more complex control procedures.
315
+
316
+ See Note in 5.2.4 above concerning differential delay.
317
+
318
+ #### 5.2.6 Data Processing Unit (DPU)
319
+
320
+ This unit is optional; when present, it contains one or both of the functions depicted as "broadcast" and "MLP" in Figure 2 and further explained below.
321
+
322
+ ##### 5.2.6.1 Data broadcast function
323
+
324
+ In this case, only one LSD and/or one HSD input can be accepted at any one time, any data subsequently arriving at another input being ignored. The data is broadcast to other outputs as determined by the control processor, according to the capability of the connected terminals to receive such data (see Recommendation H.243). Data is not echoed to the transmitter.
325
+
326
+ ##### **5.2.6.2 MLP data handling function**
327
+
328
+ In this case, the data processor is equipped to process the multilayer protocol defined in the T.120-Series Recommendations and performs one or more of the following functions (see Recommendations T.122, T.123, T.125, T.124, etc.):
329
+
330
+ - handling of telematic information according to Recommendations T.122/T.125;
331
+ - transmission of conference control signals (request/grant floor, chair control, audio/video switching, etc.) according to Recommendations T.124 and T.128 (T.AVC).
332
+
333
+ Note that as described in Recommendation H.243, the MLP data processor may also be capable of processing the simplex data protocol described in Recommendation H.224. If this is the case, appropriate capability codes shall be present in the conference SCM.
334
+
335
+ #### **5.2.7 Control processing unit**
336
+
337
+ The control processor is responsible for determining the correct routing, mixing/switching, format and timing of the audio, video, data and control signals passed to each multiplexer for outward transmission; it also deals with the processing of conference-control functions.
338
+
339
+ ##### **5.2.7.1 Incoming BAS commands**
340
+
341
+ According to the incoming BAS commands the CPU ensures the correct distribution of bits to the audio, video and data processors; it also ensures that the correct audio decoding algorithm is used on each input to the audio mixer and that any incoming data is sent to the broadcast unit or MLP processor as appropriate.
342
+
343
+ ##### **5.2.7.2 Outgoing BAS commands**
344
+
345
+ The CPU ensures that the correct audio encoding algorithm is used on each output from the audio mixer, that the desired switching or summation has been performed in each case and that the desired switching (or mixing of video signals) has been made to each output of the VPU. It transmits VCF (see Recommendation H.230) to all relevant terminals at a set time before switching the video sent to them, and transmits VCU to a terminal whose video is about to be sent to another terminal; the procedure for this is set out in Recommendation H.243.
346
+
347
+ The CPU switches mode on outgoing streams to accommodate the appropriate combination of audio, video, and data, according to the declared capabilities of the connected terminals (see Recommendation H.243). Commands MCC, MCS, MCN are transmitted to effect the appropriate mode transmissions from connected primary terminals, so that audio, video and data occupy the same capacity on all primary ports. See also Recommendation H.243.
348
+
349
+ ##### **5.2.7.3 Incoming BAS capabilities**
350
+
351
+ The capability codes from all N terminals are stored; whenever a new set is sent by a terminal, it replaces completely the previous set (exception: as a protective measure, encryption capability cannot be negated by sending a new capset with that value omitted).
352
+
353
+ ##### **5.2.7.4 Outgoing BAS capabilities**
354
+
355
+ The values to be sent to each of the N ports are determined according to Recommendations H.243 and H.242.
356
+
357
+ ##### **5.2.7.5 Conference control processing**
358
+
359
+ The conference control functions include selection of video signals to be transmitted (other than by voice-activation), selection of audio likewise, management of data tokens and the data transmission, assignment of terminal and MCU numbers, management of identity information, adding and dropping of terminals, and so on.
360
+
361
+ #### **5.2.8 Multiplexer**
362
+
363
+ The multiplexer sets up a frame structure on the outgoing channel(s) according to Recommendation H.221, and loads into this the BAS values from the CPU and the outputs of the APU, VPU and DPU.
364
+
365
+ ## 6 Multipoint configurations
366
+
367
+ **Star:** All terminals connected to a single MCU; all primary terminals are connected at the same effective bit rate, being 64 kbit/s or a multiple up to 1920 kbit/s (rates defined in Annex A/H.221); secondary terminals may be connected at a lower rate.
368
+
369
+ **Dumb-bell:** Terminals are connected to one of two MCUs, which are themselves interconnected at the same effective rate as the primary terminals.
370
+
371
+ **MCU star:** Three or more MCUs may be connected in star configuration with terminals connected to each, the MCUs being interconnected at such a bit rate that the transfer rate can be at the same level as that between each MCU and the primary terminals. A chain of three MCUs is a degenerate case of the MCU star, and so is included in the definition thereof.
372
+
373
+ **Hierarchical configurations:** The MCU star is a second-order hierarchy; higher-order configurations may be formed by adding more MCUs at the periphery of the star, as exemplified in Figure 3.
374
+
375
+ ![Diagram of an MCU hierarchical configuration showing a central MCU connected to three intermediate MCUs, which are in turn connected to four peripheral MCUs, each with terminals.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
376
+
377
+ The diagram illustrates a hierarchical MCU configuration. At the top, a central MCU is connected to three intermediate MCUs. These three intermediate MCUs are enclosed within a dashed oval. Below each intermediate MCU, there is a connection to a peripheral MCU. There are four peripheral MCUs in total. Each peripheral MCU is connected to two terminals, represented by small circles. Each intermediate MCU also has its own set of terminals, also represented by small circles. The central MCU has four terminals. The intermediate MCUs have three terminals each. The peripheral MCUs have two terminals each. The connections between MCUs are represented by solid lines. A legend at the bottom left shows a rectangle labeled 'MCU' and a circle labeled 'Terminal'. The text 'T1518820-95/d03' is located in the bottom right corner of the diagram area.
378
+
379
+ Diagram of an MCU hierarchical configuration showing a central MCU connected to three intermediate MCUs, which are in turn connected to four peripheral MCUs, each with terminals.
380
+
381
+ Figure 3/H.231 – MCU hierarchical configuration
382
+
383
+ Each link of a multipoint call is set up using the standardized point-to-point procedures of Recommendation H.320. Additional in-band provisions are described in Recommendation H.243.
384
+
385
+ ## 7 Multipoint control unit characteristics and classification
386
+
387
+ ## 7.1 Conformance
388
+
389
+ MCUs intended for use with terminals conforming with Recommendations H.221/230/242 must themselves conform to these Recommendations, and with the procedures set out in Recommendation H.243.
390
+
391
+ ## 7.2 Classification of MCUs
392
+
393
+ A wide variety of MCUs can be envisaged, according to the many different options available within the provisions of this Recommendation. Table 1 lists the various attributes and parameters which an MCU may possess, and by means of which it may be classified; the manufacturer should specify all of the properties which the unit possesses and the conditions under which they may be activated. Most of the attribute values are not themselves mandatory, but where they are provided it is mandatory that the procedures of Recommendation H.243 be adhered to. These attributes, numbered in the left-hand column of Table 1, are elaborated in 7.3 and 7.4 below, cross-referenced as [1], etc. The MCU attributes must be such as to handle the signals of the terminals with which it is intended to be used.
394
+
395
+ ## 7.3 Summary of MCU BAS capabilities
396
+
397
+ NOTE 1 – This subclause is concerned with the internal capabilities of the MCU (the BAS-capabilities declared at any time towards a particular terminal should normally take into account those of the terminals connected – see Recommendation H.243); these are a function of the physical properties of the MCU and any software selections (made automatically or by human intervention).
398
+
399
+ - a) Audio: An audio-mixing MCU intended for inter-regional operation must be able to encode and decode G.711 A-law and $\mu$ -law, and may also optionally handle other audio modes from A.5/H.221. An audio-switching MCU does not decode any audio signals; internally generated messages may be transmitted as G.711 or by other audio algorithms if appropriate [6, 6.1, 6.2].
400
+
401
+ NOTE 2 – If an MCU is not equipped with both A- and $\mu$ -law decoding it may be impossible for terminals in another region to access it.
402
+
403
+ - b) Video: An MCU may or may not be able to handle video. If it does so by switching, the different video capabilities defined in Recommendation H.221 declared by the terminals must be taken into account in determining those to be declared by the MCU, though it may have inherent video-mode capabilities of its own. Various video algorithms such as H.261, H.262, and H.263 may appear in the MCU capability set, either because terminals with such capabilities are in the conference, or because a video-mixing MCU supports these algorithms. An MCU shall support video algorithms according to the hierarchy of H.242, but need not support this hierarchy at all times. For example, an MCU may put H.263 in the conference SCM and make H.261-only terminals secondary for a particular conference, but the MCU shall support H.261 for other conferences. If an MCU supports video mixing, it may operationally put only a single video capability in the SCM, but shall still support the video algorithm hierarchy of H.242 [7, 7.1].
404
+ - c) Transfer rate: An MCU may have any of the capability values defined in Recommendation H.221 [5].
405
+ - d) Restricted-network capability: An MCU connected to a network whose B-channels are effectively restricted to $p \times 56$ kbit/s ( $p = 1$ to 24), or whose channels at 128 or higher are restricted by ones-density considerations, must declare capabilities as given in Recommendation H.221 and Recommendation H.242. All MCUs intended for interworking with terminals or MCUs on such restricted networks must have the capability to respond to appropriate restrict commands and capabilities according to Recommendations H.221 and H.242 [4.2].
406
+ - e) Data (except MLP): The MCU may or may not be capable of broadcasting data at rates up to the highest transfer rate, and may so indicate by means of the appropriate capability codes defined in Recommendation H.221 [8.1].
407
+ - f) MLP: The MCU may or may not be capable of handling MLP at rates up to the highest transfer rate, and may so indicate by means of the appropriate capability codes defined in Recommendation H.221 [8.2, 13.2].
408
+ - g) Encryption: See Recommendations H.233/H.234 [9].
409
+
410
+ - h) MBE capability: This is required for some multipoint functions (see Recommendation H.243) [16].
411
+ - i) Non-T.120 chair-control capability: The MCU may or may not be able to provide terminal numbering and the means for one terminal to control video switching, connection-dropping, etc. (see Recommendation H.243) [13.1].
412
+
413
+ Examples:
414
+
415
+ - i) A simple ISDN MCU might well possess the following capabilities:
416
+
417
+ [H.261, G.722-48 + G.728, switched video, Transfer-rate 1B and 2B and 128, LSD up to 6.4 kbit/s].
418
+ - ii) An audiographic MCU might be: [G.722-48, Transfer-rate 1B, LSD up to 14.4 kbit/s, MLP, MBE].
419
+ - iii) A videoconference MCU might be: [H.261, H.263, G.722-48, switched video, Transfer-rate 2B and H0, HSD 64 kbit/s].
420
+
421
+ ## 7.4 Other attributes
422
+
423
+ - a) Ports and configurability: A physical MCU equipment may be capable of handling several simultaneous independent conferences, with limitations as to number of possible connections to terminals and to other MCUs [1, 2, 3].
424
+ - b) Network aspects: An MCU may be designed for connection to various types of digital networks, with various call-control arrangements, including the possibility of using the same network address for all incoming connections to a given conference [4.1, 13].
425
+ - c) Communication mode selection: Various possibilities exist for the method of selection of "Selected Communication Mode" (see Recommendation H.243) and the resultant treatment of connected terminals as "primary" or "secondary" [10, 11].
426
+ - d) Terminal identification: An MCU may or may not be able to request, accept and process alphanumeric strings from connected terminals for identification purposes (see Recommendation H.243) [15].
427
+ - e) Cascading: An MCU may be capable of operating with another MCU to provide "cascaded" operation. Cascading may be limited to two MCUs per conference, or may extend to a "star" configuration, and finally to a multi-level hierarchy. Two mechanisms for cascading exist:
428
+ - i) fixed rates ("simple") [14.1];
429
+ - ii) master/slave operation, required for many features such as terminal numbering [14.2].
430
+
431
+ ## 8 "Listed" multipoint control units
432
+
433
+ Table 1 lists the present set of attributes, as well as possible values for certain attributes, that can be associated with a multipoint control unit. Table 1 is meant to act as a guide to users to determine what attributes an MCU could possess and is not exhaustive.
434
+
435
+ Given the very wide range of possible MCU properties and capabilities, it is appropriate to identify a rather narrower range which can be referred to for clarity and convenience, without any implication that other conformant MCUs are in any way non-standard. This narrower range is more exactly defined and understood, and applicable to fairly common service implementations using terminals which may be widely available and not highly specialized. The listed MCUs are presented in Table 2.
436
+
437
+ The listed MCUs have relatively few options. Manufacturers may include in a given product one (or more) of the listed types, thus assuring a customer of a known range of behaviour when used with equipment from other manufacturers; "enhancements" of various types could also be included and would themselves be in conformance with available Recommendations, but the behaviour when used with other equipment might be less predictable or give problems of complexity at the human-machine interface.
438
+
439
+ ## 9 Terminal requirements and options
440
+
441
+ All terminals must conform to the provisions of Recommendations H.221, H.230 and H.242.
442
+
443
+ A terminal intended for chair-control operation (see Recommendation H.243) must be able to transmit BAS codes and provide other functions as described in 9.1/H.243.
444
+
445
+ **Table 1/H.231 – MCU attributes**
446
+
447
+ | | Attribute | Possible values |
448
+ |-----|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
449
+ | 1 | Maximum number of terminals that can be connected to a single MCU | 3, 4, 5 ... |
450
+ | 2 | Maximum number of concurrent (independent) conferences that can be supported in a single MCU | 1, 2, 3 ... |
451
+ | 3 | Maximum number of ports that can be connected to other MCUs [if non-zero state whether item (1) is dependent] | 0, 1, 2 ... |
452
+ | 4.1 | Network interfaces at each port (if not all the same, give details) | BRI, PRI, E1/T1/J1, ATM, other |
453
+ | 4.2 | Restricted network capability | Restrict_Required, Restrict_P, Restrict_L, No_Restrict |
454
+ | 5 | Transfer rates available at each port (if not all identical, give details) | Any capability values from Rec. H.221 |
455
+ | 6 | Audio processor | Mandatory |
456
+ | 6.1 | Mixed/switched (give details)<br>Noise/echo suppression on "silent" ports | Mixed; auto- or user-switched (see [13.2])<br>Give details |
457
+ | 6.2 | audio algorithm at each port<br>Rec. G.711<br>Rec. G.728<br>Rec. G.722 | <br>Yes/No<br>Yes/No<br>Yes/No |
458
+ | 7 | Video processor (moving pictures) | No/Yes (details below) |
459
+ | 7.1 | Switched/mixed (give details) | Switched automatically (speech power basis)/user-control (see [13.2]), mixed |
460
+ | 7.2 | Video algorithm at each port<br>Rec. H.261<br>Rec. H.262<br>Rec. H.263 | <br>Yes/No<br>Yes/No<br>Yes/No |
461
+ | 8 | Data processor | |
462
+ | 8.1 | Data broadcast facility, LSD<br>Data broadcast facility, HSD | No/Yes + rates from Rec. H.221<br>No/Yes + rates from Rec. H.221 |
463
+ | 8.2 | MLP processor | No/Yes + rates from Rec. H.221 |
464
+ | 9 | Encryption | Not supported, supported (details, algorithm, etc.) |
465
+ | 10 | Method of choosing Selected Communications Mode (SCM) | Preset by manufacturer (give values)<br>Set by operator input (give range)<br>Set by user (give range) (see [13.2])<br>Auto-set according to conn. terminals (details) |
466
+
467
+ **Table 1/H.231 – MCU attributes (concluded)**
468
+
469
+ | | <b>Attribute</b> | <b>Possible values</b> |
470
+ |------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
471
+ | 11 | Can deal with secondary terminals | Yes/No + details |
472
+ | 12 | Call set-up provision(s) | Non-reservation/reservation (+ details)<br>Auto-answer at all ports (give numbering system)<br>Operator set-up<br>Dial out |
473
+ | 13 | Control capabilities | |
474
+ | 13.1 | Numbering of terminals<br>Simple chair control using BAS | Yes/No<br>Yes/No |
475
+ | 13.2 | MLP facilities<br>[refer to ITU-T T-series] | No/Yes |
476
+ | 13.3 | H.224 (simplex data) | H.224_LSD, H.224_HSD, H.224_MLP, H.224_sim |
477
+ | 14 | Cascading | Yes/No |
478
+ | 14.1 | Fixed rates ("simple") | Yes/No |
479
+ | 14.2 | Master/slave | Yes/No |
480
+ | 15 | Terminal identification | No/TCI/TCS |
481
+ | 16 | MBE capability | Yes/No |
482
+
483
+ **Table 2/H.231 – Listed MCUs**
484
+
485
+ | | | MCU Type and values | | | | | | |
486
+ |-----------|----------------------------------------------------------------------------------------------------------------------|---------------------|-------------------|-----------------------|---------------|-----------------------|---------------|---------------|
487
+ | Attribute | | A | B(d) | C | C2 | C(d) | D | D(d) |
488
+ | 1 | Maximum number of terminals that can be connected to a single MCU | | | | | | | |
489
+ | 2 | Maximum number of concurrent (independent) conferences that can be supported in a single MCU | | | | | | | |
490
+ | 3 | Maximum number of ports that can be connected to other MCUs [if non-zero, state whether item [1] above is dependent] | | | | | | | |
491
+ | 4.1 | Network interfaces at each port (if not all the same, give details) | | | | | | | |
492
+ | 4.2 | Restricted network capability | | | | | | | |
493
+ | 5 | Transfer rates available at each port | 64k | 64k | 2B | 2B | 2B | H0 | H0 |
494
+ | 6 | Audio processor | | | | | | | |
495
+ | 6.1 | Mixed/switched (give details)<br>Noise/echo suppression on "silent" ports | switched | switched | switched | switched | switched | switched | switched |
496
+ | 6.2 | Audio algorithm at each port | G.728 + G.711 | G.722 + G.711 | G.722 + G.728 + G.711 | G.728 + G.711 | G.722 + G.728 + G.711 | G.722 + G.711 | G.722 + G.711 |
497
+ | 7 | Video processor (moving pictures) | Yes | a) | Yes | Yes | Yes | Yes | Yes |
498
+ | 7.1 | Switched/mixed (give details) | switch | a) | switch | switch | switch | switch | switch |
499
+ | 7.2 | Video algorithm at each port | H.261 | a) | H.261 | H.261 | H.261 | H.261 | H.261 |
500
+ | 8 | Data processor | a) | Yes | a) | a) | Yes | a) | Yes |
501
+ | 8.1 | Data broadcast facility, LSD<br>Data broadcast facility, HSD | | up to 14.4k<br>a) | | | up to 14.4k<br>a) | | b)<br>b) |
502
+ | 8.2 | MLP Processor | a) | a) | a) | a) | a) | a) | a) |
503
+ | 9 | Encryption | a) | a) | a) | a) | a) | a) | a) |
504
+ | 10 | Method of choosing Selected Communications Mode (SCM) | | | | | | | |
505
+
506
+ **Table 2/H.231 – Listed MCUs (concluded)**
507
+
508
+ | | | MCU Type and values | | | | | | |
509
+ |-----------|----------------------------------------------------------|---------------------|----------|----------|----------|----------|----------|----------|
510
+ | Attribute | | A | B(d) | C | C2 | C(d) | D | D(d) |
511
+ | 11 | Can deal with secondary terminals as audio only | Yes | Yes | Yes | Yes | Yes | Yes? | Yes? |
512
+ | 12 | Call set-up provision(s) | | | | | | | |
513
+ | 13 | Control capabilities | | | | | | | |
514
+ | 13.1 | Numbering of terminals<br>Simple chair control using BAS | a)<br>a) | a)<br>a) | a)<br>a) | a)<br>a) | a)<br>a) | a)<br>a) | a)<br>a) |
515
+ | 13.2 | MLP facilities | a) | a) | a) | a) | a) | a) | a) |
516
+ | 13.3 | H.224 (simplex data) | a) | a) | a) | a) | a) | a) | a) |
517
+ | 14 | Cascading | a) | a) | a) | a) | a) | a) | a) |
518
+ | 15 | Terminal identification | a) | a) | a) | a) | a) | a) | a) |
519
+ | 16 | MBE capability | a) | a) | a) | a) | a) | a) | a) |
520
+
521
+ a) Means that when set to work as the listed type, such facilities, if present, are disabled. Where there is no entry, implementers are free to use appropriate options.
522
+
523
+ b) LSD and HSD maximum rates are for further study.
524
+
525
+ ## ITU-T RECOMMENDATIONS SERIES
526
+
527
+ | | |
528
+ |-----------------|--------------------------------------------------------------------------------------------------------------------------------|
529
+ | Series A | Organization of the work of the ITU-T |
530
+ | Series B | Means of expression: definitions, symbols, classification |
531
+ | Series C | General telecommunication statistics |
532
+ | Series D | General tariff principles |
533
+ | Series E | Overall network operation, telephone service, service operation and human factors |
534
+ | Series F | Non-telephone telecommunication services |
535
+ | Series G | Transmission systems and media, digital systems and networks |
536
+ | <b>Series H</b> | <b>Audiovisual and multimedia systems</b> |
537
+ | Series I | Integrated services digital network |
538
+ | Series J | Transmission of television, sound programme and other multimedia signals |
539
+ | Series K | Protection against interference |
540
+ | Series L | Construction, installation and protection of cables and other elements of outside plant |
541
+ | Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
542
+ | Series N | Maintenance: international sound programme and television transmission circuits |
543
+ | Series O | Specifications of measuring equipment |
544
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
545
+ | Series Q | Switching and signalling |
546
+ | Series R | Telegraph transmission |
547
+ | Series S | Telegraph services terminal equipment |
548
+ | Series T | Terminals for telematic services |
549
+ | Series U | Telegraph switching |
550
+ | Series V | Data communication over the telephone network |
551
+ | Series X | Data networks and open system communication |
552
+ | Series Z | Programming languages |
marked/H/T-REC-H.233-200211-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg ADDED

Git LFS Details

  • SHA256: 29be6c2ab50c32250315313e97de8e7b875debaa14d8d93fecf928e186df5281
  • Pointer size: 131 Bytes
  • Size of remote file: 124 kB
marked/H/T-REC-H.233-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
  • Pointer size: 129 Bytes
  • Size of remote file: 8.25 kB